Commit c27c38af authored by Viresh Kumar's avatar Viresh Kumar Committed by Rafael J. Wysocki

Documentation: cpufreq: Update policy notifier documentation

Update documentation with the recent policy notifier updates.
Signed-off-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
parent df0eea44
...@@ -57,19 +57,11 @@ transition notifiers. ...@@ -57,19 +57,11 @@ transition notifiers.
2.1 CPUFreq policy notifiers 2.1 CPUFreq policy notifiers
---------------------------- ----------------------------
These are notified when a new policy is intended to be set. Each These are notified when a new policy is created or removed.
CPUFreq policy notifier is called twice for a policy transition:
1.) During CPUFREQ_ADJUST all CPUFreq notifiers may change the limit if The phase is specified in the second argument to the notifier. The phase is
they see a need for this - may it be thermal considerations or CPUFREQ_CREATE_POLICY when the policy is first created and it is
hardware limitations. CPUFREQ_REMOVE_POLICY when the policy is removed.
2.) And during CPUFREQ_NOTIFY all notifiers are informed of the new policy
- if two hardware drivers failed to agree on a new policy before this
stage, the incompatible hardware shall be shut down, and the user
informed of this.
The phase is specified in the second argument to the notifier.
The third argument, a void *pointer, points to a struct cpufreq_policy The third argument, a void *pointer, points to a struct cpufreq_policy
consisting of several values, including min, max (the lower and upper consisting of several values, including min, max (the lower and upper
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment