View Single Post
Posts: 159 | Thanked: 68 times | Joined on Sep 2011 @ India
#2220
Originally Posted by blackjack4it View Post
I'm testing the following power profile ('overclock' in batterypatch) that I've edited basing on starving profile and dsp profile, it gives the voltage when needed and when you don't record anything it uses starving voltages:
Code:
# DO NOT EDIT THIS FILE - CREATE A COPY OF IT FOR CUSTOMIZATION 
# minimum frequency to use
MINFREQ=500
# maximum frequency to use
MAXFREQ=900
# list of frequency configurations: each "frequency:volt,dsprate"
FREQS="0:22,90 125:22,90 250:28,180 500:29,360 550:32,400 600:34,430 720:54,520 805:54,600 850:54,600 900:54,600 950:60,600 1000:60,600 1100:72,600 1150:72,600"
SMARTREFLEX_VDD1=1
SMARTREFLEX_VDD2=1
GOVERNOR=ondemand
UP_THRESHOLD=95
SAMPLING_RATE=300000
IGNORE_NICE_LOAD=0
POWERSAVE_BIAS=0
No reboot till yesterday, I've set starving voltages in 0-600 range , dspprofile voltages in the rest of frequences and 500 as min freq as my kp48 starving profile.
I use also this profile when in standby ('underclock' in batterypatch):
Code:
MINFREQ=125
MAXFREQ=250
FREQS="0:22,90 125:22,90 250:28,180 500:29,360"
SMARTREFLEX_VDD1=1
SMARTREFLEX_VDD2=1
GOVERNOR=ondemand
UP_THRESHOLD=95
SAMPLING_RATE=300000
IGNORE_NICE_LOAD=0
POWERSAVE_BIAS=0
This extends the standby time, because it consumes more power only when needed...the dsp default profile eat my N900 O_O
i think latest kernel-power with sr_vdd1 enabled does not depend upon the values you have set in the profile u are using...sr calculates its own values and saves it and then uses the previously calculated value for a particular frequency as a benchmark for the next time...

so IMHO setting too low voltages in the profile has no effect on the actual voltages..

i will be highly obliged if somebody corrects me if i am wrong...

thanks

EDIT :
i cant say anything about kp48

Last edited by knobby; 2011-11-22 at 09:15.
 

The Following 2 Users Say Thank You to knobby For This Useful Post: