12/19: Need testers for kernel that can simultaneously battery save and overclock

[shikyo]

I have a tilt2 and I run Sleep Mode 0 with overclock at 671744. Thats 656Mhz. Short of the usual 768 I did but it gives me sleep mode 0 stable and better battery life... when its asleep. You know its fully asleep when the light turns green.

[manekineko]

Originally Posted by shikyo

I have a tilt2 and I run Sleep Mode 0 with overclock at 671744. Thats 656Mhz. Short of the usual 768 I did but it gives me sleep mode 0 stable and better battery life... when its asleep. You know its fully asleep when the light turns green.

You managed to run both sleep mode 0 and overclock at the same time? Can you post your startup.txt? I'd like to try that.

[zeurx]

just leave the pm options out and run oc options... but this way 12% in around 6-7 hrs

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz

set cmdline "lcd.density=240 7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsens
or_axis=2,1,3 rel_path=andboot hw3d.force=1 acpuclock.oc_freq_khz=726000 physkey
board=rhod500 force_cdma=1"

[arrrghhh]

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz

set cmdline "lcd.density=240 7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 rel_path=andboot hw3d.force=1 acpuclock.oc_freq_khz=726000 physkeyboard=rhod500 force_cdma=1"

Just to let you know, there were a couple of deprecated commands in your startup. They're in bold/red. They shouldn't hurt anything, but there's no need for them either.

[bzo]

I have a fix for using sleep mode of 1 while overclocked. I haven't tested 0, but it should work if 0 works normally. I was under the impression that the sleep mode of 0 was broken.

Test kernel attached. I'll get the patch submitted as soon as I get at least a few reports of success.

[manekineko]

Originally Posted by bzo

I have a fix for using sleep mode of 1 while overclocked. I haven't tested 0, but it should work if 0 works normally. I was under the impression that the sleep mode of 0 was broken.

Test kernel attached. I'll get the patch submitted as soon as I get at least a few reports of success.

I can confirm that at least initially, your fix appears to work.

I tested this by adding overclock, and setting sleep mode to 1 on a regular kernel. I then booted my phone 3 times and put it to sleep, waiting until the green light came on (this actually took quite a few more than 3 boots, because most of the time the green light would never come on). After the green light came on, I attempted to wake the phone with the power button. In all 3 cases, the green light changed orange but the phone did not wake.

I then installed your kernel, while keeping everything else the same. I booted, and then put the phone to sleep. Green light came on, I successfully woke the phone.

What was the cause of the issue?

I'm going to update first post and ask for more testers.

[bzo]

Originally Posted by manekineko

What was the cause of the issue?

Normally, the PLL2 clock is setup to run at 1056mhz and divided by 2 for the regular 528mhz top speed of the cpu. The max speed of PLL2 is 1200mhz, so if a 2 divider is used, the max frequency possible is 600mhz. So for overclocking, we skip the divider and use the frequency directly so that frequencies above 600mhz are possible.

It appears that in the deeper sleep modes, the clocks are automatically being shut down and powered up again on wake up. The wakeup assumes that PLL2 should be brought back up to 1056mhz and does not reset the divider back to 2, so the cpu is trying to run at 1056mhz which will obviously not work.

The fix checks that PLL2 is being run at the frequency we expect at wakeup or whenever the cpu frequency is changed, and corrects if necessary.