Documentation/cpu-freq/cpu-drivers.rst

48  .init - A pointer to the per-policy initialization function.
68  .exit - A pointer to a per-policy cleanup function called during
71  .suspend - A pointer to a per-policy suspend function which is called
73  policy.
75  .resume - A pointer to a per-policy resume function which is called
78  .ready - A pointer to a per-policy ready function which is called after
79  the policy is fully initialized.
86  .set_boost - A pointer to a per-policy function to enable/disable boost
94 cpufreq driver registers itself, the per-policy initialization function
95 cpufreq_driver.init is called if no cpufreq policy existed for the CPU.
97 policy and not for each CPU managed by the policy. It takes a ``struct
98 cpufreq_policy *policy`` as argument. What to do now?
105 |policy->cpuinfo.min_freq _and_	    |					   |
106 |policy->cpuinfo.max_freq	    | the minimum and maximum frequency	   |
110 |policy->cpuinfo.transition_latency | the time it takes on this CPU to	   |
115 |policy->cur			    | The current operating frequency of   |
118 |policy->min,			    |					   |
119 |policy->max,			    |					   |
120 |policy->policy and, if necessary,  |					   |
121 |policy->governor		    | must contain the "default policy" for|
128 |policy->cpus			    | Update this with the masks of the	   |
134 For setting some of these values (cpuinfo.min[max]_freq, policy->min[max]), the
142 When the user decides a new policy (consisting of
143 "policy,governor,min,max") shall be set, this policy must be validated
145 values cpufreq_verify_within_limits(``struct cpufreq_policy *policy``,
150 range) is within policy->min and policy->max. If necessary, increase
151 policy->max first, and only if this is no solution, decrease policy->min.
169 The target_index call has two arguments: ``struct cpufreq_policy *policy``,
175 It should always restore to earlier frequency (i.e. policy->restore_freq) in
180 The target call has three arguments: ``struct cpufreq_policy *policy``,
187 - policy->min <= new_freq <= policy->max (THIS MUST BE VALID!!!)
204 This function has two arguments: ``struct cpufreq_policy *policy`` and
211 The setpolicy call only takes a ``struct cpufreq_policy *policy`` as
213 in-chipset dynamic frequency switching to policy->min, the upper limit
214 to policy->max, and -if supported- select a performance-oriented
215 setting when policy->policy is CPUFREQ_POLICY_PERFORMANCE, and a
234 NOTE: ->target_index() should restore to policy->restore_freq in case of
253 The cpufreq table is verified automatically by the core if the policy contains a
254 valid pointer in its policy->freq_table field.
257 frequency is within policy->min and policy->max, and all other criteria