AuxXxilium/linux_dsm_epyc7002
1
0
Fork 0
mirror of https://github.com/AuxXxilium/linux_dsm_epyc7002.git synced 2025-04-19 14:27:50 +07:00
Code Issues Actions Packages Projects Releases Wiki Activity

Documentation: cpufreq: Update policy notifier documentation

Browse Source 
Update documentation with the recent policy notifier updates.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
This commit is contained in:
Viresh Kumar 2019-07-23 11:44:10 +05:30 committed by Rafael J. Wysocki
parent df0eea4488
commit c27c38afd8
1 changed files with 4 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Documentation/cpu-freq/core.txt
View File

@ -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