[kernel][Overclocked] Overclocked kernel

[Guest jsplace]

But there's another user whose phone started to show artifacts after applying steve's OCed kernel. I suppose that's because real speed was actually changed?

I wasn't using Steves Kernel. I was using my own. The clocks file was based around changes I did for my Hero kernel modified for MSM7227 and did indeed incorporate similar changes to Kallt's acpuclock.c

My Linpack scores went from 3.7 @ 600Mhz to 4.7 @ 806Mhz

After looking at battery life, heat and the inability to charge via USB at 806Mhz I will not be running this high.

Will be doing some further testing today at lower freqs to see if I can find a happy medium that gets a good balance of battery vs performance and will still allow USB charging with wifi, bluetooth and/or screen on.

@Kallt. Do you know the full format of the cpuclock file? Is an undervolt possible?

[Guest Maringer]

@Kallt. Do you know the full format of the cpuclock file? Is an undervolt possible?

Hopefully undervolt will be available. I'm happy enough with the performance of the SF so any extra battery life would be useful.

We can only hope for the holy grail of both undervolt and overclock at the same time... :)

[Guest mELIANTE]

I wasn't using Steves Kernel. I was using my own. The clocks file was based around changes I did for my Hero kernel modified for MSM7227 and did indeed incorporate similar changes to Kallt's acpuclock.c

Ops! Sorry for that :)

[Guest kallt_kaffe]

@Kallt. Do you know the full format of the cpuclock file? Is an undervolt possible?

	   { 0, 120000, ACPU_PLL_1, 1, 7,  60000, 1, 3,  61440 },

		{ 1, 122880, ACPU_PLL_0, 4, 1,  61440, 1, 3,  61440 },

		{ 0, 200000, ACPU_PLL_2, 2, 5,  66667, 2, 4,  61440 },

		{ 1, 245760, ACPU_PLL_0, 4, 0, 122880, 1, 4,  61440 },

		{ 1, 320000, ACPU_PLL_1, 1, 2, 160000, 1, 5, 122880 },

		{ 0, 400000, ACPU_PLL_2, 2, 2, 133333, 2, 5, 122880 },

		{ 1, 480000, ACPU_PLL_1, 1, 1, 160000, 2, 6, 122880 },

		{ 1, 600000, ACPU_PLL_2, 2, 1, 200000, 2, 7, 122880 },[/code]


I think the 2nd value from the right may control the voltage. I basing this assumption on this information: http://forum.xda-developers.com/showthread.php?t=665909

In that example (Hero overclocking) that value is using constant defined elsewhere but named VDD_7 which propably translates to 7.


If that is true then 480MHz uses a lower voltage setting than 600000 and so on, makes sense.

[Guest cobhc]

	   { 0, 120000, ACPU_PLL_1, 1, 7,  60000, 1, 3,  61440 },

		{ 1, 122880, ACPU_PLL_0, 4, 1,  61440, 1, 3,  61440 },

		{ 0, 200000, ACPU_PLL_2, 2, 5,  66667, 2, 4,  61440 },

		{ 1, 245760, ACPU_PLL_0, 4, 0, 122880, 1, 4,  61440 },

		{ 1, 320000, ACPU_PLL_1, 1, 2, 160000, 1, 5, 122880 },

		{ 0, 400000, ACPU_PLL_2, 2, 2, 133333, 2, 5, 122880 },

		{ 1, 480000, ACPU_PLL_1, 1, 1, 160000, 2, 6, 122880 },

		{ 1, 600000, ACPU_PLL_2, 2, 1, 200000, 2, 7, 122880 },[/code]


I think the 2nd value from the right may control the voltage. I basing this assumption on this information: http://forum.xda-developers.com/showthread.php?t=665909

In that example (Hero overclocking) that value is using constant defined elsewhere but named VDD_7 which propably translates to 7.


If that is true then 480MHz uses a lower voltage setting than 600000 and so on, makes sense.


That seems pretty logical to me looking at the table you posted above. Any way of checking the voltage/heat of the cpu to see if the undervolting works without having to test battery usage?

[Guest jsplace]

Does the CPU even have a temp sensor? If it does then its possible.

[Guest Stephen Hyde]

no the arm cpus dont have temp sensors - i will try using your acpuclock kallt_kaffee and see if it is different - apologies for acting like an idiot - my first attempt at overclocking a device

[Guest Stephen Hyde]

ok that acpuclock doesnt work at all just causes a reboot loop

[Guest kallt_kaffe]

ok that acpuclock doesnt work at all just causes a reboot loop

Did you enable any overclocking and if you did, how high you try to go? Reboot loop is what I get on my U8100 if I try to go to high.

jsplace, can you post your acpuclock.c? And Stephen, could you point me to the overclocked Legend code you based your first code on. I'm sure there should be code similar to the one I posted above it that file. Unless your reboot loop is because of to much overclocking there may some slight differences on how to do the trick on a 7627 CPU.

I cannot test anything for the blade myself as I don't have one but I'll try to help if I can.

Edited November 3, 2010 by kallt_kaffe

[Guest oh!dougal]

In another thread ...

2.1 (modaco r4) at min since 2.2 doesn play nice with touch screen at min

quadrant of 398 (but bear in mind 2.1 is crap in cpu benches anyway)

havnt tried over/undervolting at all not 100% sure of the layout of clock file.

so its running at stock voltage, battery dispaly is broken so i cant give idea on batt yet

I did think that seemed rather like standard.

Is that the region that this thing is currently scoring?

[Guest Stephen Hyde]

Did you enable any overclocking and if you did, how high you try to go? Reboot loop is what I get on my U8100 if I try to go to high.

jsplace, can you post your acpuclock.c? And Stephen, could you point me to the overclocked Legend code you based your first code on. I'm sure there should be code similar to the one I posted above it that file. Unless your reboot loop is because of to much overclocking there may some slight differences on how to do the trick on a 7627 CPU.

I cannot test anything for the blade myself as I don't have one but I'll try to help if I can.

https://github.com/aleho/htc-kernel-legend/...puclock-arm11.c << legend code

i tried 806 and 864 (06 being what legend is stable at so should be what the blade can in theory handle

[Guest jsplace]

I won't be at home until Friday morning now but will post my cpuclock file as soon as I am back.

[Guest Maringer]

https://github.com/aleho/htc-kernel-legend/...puclock-arm11.c << legend code

i tried 806 and 864 (06 being what legend is stable at so should be what the blade can in theory handle

Just a guess, but perhaps the Legend (being a much more expensive device than the SF) has a better/larger heatsink? This could explain why overclocking might not work as well on the SF.

I've no experience whatsoever of overclocking a phone so take this comment at face value - I could be completely incorrect.

[Guest kallt_kaffe]

Change 0x33c to 0x304

[Guest Stephen Hyde]

ok boots using that acpuclock on stock freqs (all overclocks commented)

[Guest Stephen Hyde]

update bootloop starts as soon as i try any form of overclock

[Guest Rem1x]

Ok, aside from stuff like games and benchmarks this 2.1 ROM is much quicker then froyo.

Which I feel means. Something is wrong with FroYo.

Just throwing that out there.

[Guest kallt_kaffe]

update bootloop starts as soon as i try any form of overclock

Have you tried changing:

writel(hunt_s->a11clk_khz/19200, MSM_CLK_CTL_BASE+0x33C);

To:

writel(hunt_s->a11clk_khz/19200, MSM_CLK_CTL_BASE+0x304);

+304 is what the Legend uses in the source you pointed to.

[Guest Stephen Hyde]

yep it crashes even with it set to 304 - any level odf overclock causes it even the smallest step

[Guest kallt_kaffe]

yep it crashes even with it set to 304 - any level odf overclock causes it even the smallest step

Maybe the Hero method doesn't work on the blade, or maybe I did something stupid. jsplace had it working, confirmed with benchmarks so his source can propably solve the mystery once he post it.

[Guest Stephen Hyde]

yup my thinking too :)

[Guest kallt_kaffe]

I got my Blade two days ago and I've started looking at overclocking now (Spent the first two days making a ROM: http://www.mediafire.com/?yzz9wv8wnz5atcm )

My original acpuclock.c works for me but 806MHz is no-go... I'm currently running at 729.6MHz.

Here's some benchmarks (SetCPU Native 3 runs and then 2 linpack runs)

600MHz 3299 3298 3522 3.6 3.7

672MHz 2972 2952 2962

710MHz 2733 2750 2751 4.3 4.2

730MHz 2654 2624 2685 4.3 4.4

749MHz -freezes with bootlogo-

EDIT: Even 729.6MHz (730) freezes at boot sometimes so I'm currently using 710.4MHz.

EDIT2: 710.4MHz kernel to go with my ROM (se link above): http://www.mediafire.com/?jn52ivxexx7sps6 (batterymeter not working)

Now, did you (or anyone else) find a solution to the battery indicator problem? That's all that I've noticed that isn't working (fixed the powerbutton with your keylayout file).

Edited November 12, 2010 by kallt_kaffe

[Guest Stephen Hyde]

I got my Blade two days ago and I've started looking at overclocking now (Spent the first two days making a ROM: http://www.mediafire.com/?yzz9wv8wnz5atcm )

My original acpuclock.c works for me but 806MHz is no-go... I'm currently running at 729.6MHz.

Here's some benchmarks (SetCPU Native 3 runs and then 2 linpack runs)

600MHz 3299 3298 3522 3.6 3.7

672MHz 2972 2952 2962

710MHz 2733 2750 2751 4.3 4.2

730MHz 2654 2624 2685 4.3 4.4

749MHz -freezes with bootlogo-

EDIT: Even 729.6MHz (730) freezes at boot sometimes so I'm currently using 710.4MHz.

EDIT2: 710.4MHz kernel to go with my ROM (se link above): http://www.mediafire.com/?jn52ivxexx7sps6 (batterymeter not working)

Now, did you (or anyone else) find a solution to the battery indicator problem? That's all that I've noticed that isn't working (fixed the powerbutton with your keylayout file).

i fixed battery a while back :rolleyes: fancy throwing me a copy of your acpuclock and ill up it to my repo also

[Guest cobhc]

Is wireless working on this kallt?

[Guest kallt_kaffe]

Is wireless working on this kallt?

Yes