|author||Mark Brown <email@example.com>||2010-11-11 01:51:26 +0100|
|committer||Rafael J. Wysocki <firstname.lastname@example.org>||2010-11-11 01:51:26 +0100|
PM / OPP: Hide OPP configuration when SoCs do not provide an implementation
Since the OPP API is only useful with an appropraite SoC-specific implementation there is no point in offering the ability to enable the API on general systems. Provide an ARCH_HAS OPP Kconfig symbol which masks out the option unless selected by an implementation. Signed-off-by: Mark Brown <email@example.com> Acked-by: Nishanth Menon <firstname.lastname@example.org> Acked-by: Kevin Hilman <email@example.com> Signed-off-by: Rafael J. Wysocki <firstname.lastname@example.org>
Diffstat (limited to 'Documentation')
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/power/opp.txt b/Documentation/power/opp.txt
index 44d87ad3cea..cd445582d1f 100644
@@ -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.