|author||Mark Brown <email@example.com>||2014-07-22 15:43:12 +0100|
|committer||Rafael J. Wysocki <firstname.lastname@example.org>||2014-07-23 00:51:30 +0200|
PM / OPP: Remove ARCH_HAS_OPP
Since the OPP layer is a kernel library which has been converted to be directly selectable by its callers rather than user selectable and requiring architectures to enable it explicitly the ARCH_HAS_OPP symbol has become redundant and can be removed. Do so. Signed-off-by: Mark Brown <email@example.com> Reviewed-by: Viresh Kumar <firstname.lastname@example.org> Acked-by: Nishanth Menon <email@example.com> Acked-by: Rob Herring <firstname.lastname@example.org> Acked-by: Shawn Guo <email@example.com> Acked-by: Simon Horman <firstname.lastname@example.org> Signed-off-by: Rafael J. Wysocki <email@example.com>
Diffstat (limited to 'Documentation/power')
1 files changed, 0 insertions, 3 deletions
diff --git a/Documentation/power/opp.txt b/Documentation/power/opp.txt
index a9adad828cdc..c6279c2be47c 100644
@@ -51,9 +51,6 @@ 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.