Lines Matching refs:governor
65 and CPUfreq governor to be used
68 / the cpufreq governor decides
87 The CPUfreq governor "performance" sets the CPU statically to the
95 The CPUfreq governor "powersave" sets the CPU statically to the
103 The CPUfreq governor "userspace" allows the user, or any userspace
112 The CPUfreq governor "ondemand" sets the CPU depending on the
173 when ondemand governor would have targeted 1000 MHz, it will target
179 frequency is chosen instead of ondemand governor's original target.
195 The CPUfreq governor "conservative", much like the "ondemand"
196 governor, sets the CPU depending on the current usage. It differs in
200 The governor is tweaked in the same manner as the "ondemand" governor
208 it behave identically to the "ondemand" governor.
211 governor but for the opposite direction. For example when set to its
215 sampling_down_factor: similar functionality as in "ondemand" governor.
224 A new governor must register itself with the CPUfreq core using
228 governor->name - A unique name for this governor
229 governor->governor - The governor callback function
230 governor->owner - .THIS_MODULE for the governor module (if
233 The governor->governor callback is called with the current (or to-be-set)
237 CPUFREQ_GOV_START: This governor shall start its duty for the CPU
239 CPUFREQ_GOV_STOP: This governor shall end its duty for the CPU
249 The CPUfreq governor may call the CPU processor driver using one of
261 What's the difference between these two functions? When your governor
262 still is in a direct code path of a call to governor->governor, the