---

yaml --- r: 222167 b: refs/heads/master c: 43e6086 h: refs/heads/master i: 222165: d3d9edf 222163: c821609 222159: ba32f2a v: v3
git-mirror · Nov 11, 2010 · da05d62 · da05d62
1 parent 9aede66
commit da05d62
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 1 deletion.
diff --git a/[refs] b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: d08a5ace18dce9b18d8eb56bb6c0feef082b1b33
+refs/heads/master: 43e60861fe9d39740cf5b355f58fecedf0d8e9ba
diff --git a/trunk/Documentation/power/opp.txt b/trunk/Documentation/power/opp.txt
@@ -37,6 +37,9 @@ Typical usage of the OPP library is as follows:
 SoC framework	-> modifies on required cases certain OPPs	-> OPP layer
 		-> queries to search/retrieve information	->
 
+Architectures that provide a SoC framework for OPP should select ARCH_HAS_OPP
+to make the OPP layer available.
+
 OPP layer expects each domain to be represented by a unique device pointer. SoC
 framework registers a set of initial OPPs per device with the OPP layer. This
 list is expected to be an optimally small number typically around 5 per device.

diff --git a/trunk/kernel/power/Kconfig b/trunk/kernel/power/Kconfig
@@ -246,9 +246,13 @@ config PM_OPS
 	depends on PM_SLEEP || PM_RUNTIME
 	default y
 
+config ARCH_HAS_OPP
+	bool
+
 config PM_OPP
 	bool "Operating Performance Point (OPP) Layer library"
 	depends on PM
+	depends on ARCH_HAS_OPP
 	---help---
 	  SOCs have a standard set of tuples consisting of frequency and
 	  voltage pairs that the device will support per voltage domain. This