summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorNishanth Menon <nm@ti.com>2011-06-10 20:24:57 +0200
committerRafael J. Wysocki <rjw@sisk.pl>2011-07-15 23:58:18 +0200
commit99f381d3549432a250fe846a2a82d61a032804b0 (patch)
treec267e27c99d0609732e54fb7e7fda9fef2a7e8c0 /Documentation
parent3110df800c4de2724624d46e6bed27efc5e9a707 (diff)
PM / OPP: Introduce function to free cpufreq table
cpufreq table allocated by opp_init_cpufreq_table is better freed by OPP layer itself. This allows future modifications to the table handling to be transparent to the users. Signed-off-by: Nishanth Menon <nm@ti.com> Acked-by: Kevin Hilman <khilman@ti.com> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/power/opp.txt2
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/power/opp.txt b/Documentation/power/opp.txt
index 5ae70a12c1e2..3035d00757ad 100644
--- a/Documentation/power/opp.txt
+++ b/Documentation/power/opp.txt
@@ -321,6 +321,8 @@ opp_init_cpufreq_table - cpufreq framework typically is initialized with
addition to CONFIG_PM as power management feature is required to
dynamically scale voltage and frequency in a system.
+opp_free_cpufreq_table - Free up the table allocated by opp_init_cpufreq_table
+
7. Data Structures
==================
Typically an SoC contains multiple voltage domains which are variable. Each