summaryrefslogtreecommitdiffstats
path: root/drivers/base
diff options
context:
space:
mode:
authorViresh Kumar <viresh.kumar@linaro.org>2016-12-01 16:28:15 +0530
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-12-06 02:27:58 +0100
commit579c49efdf5a04869b29891e46cde0ed4df5480a (patch)
tree6289138cdbd46e70e12fcce1bd1b7a2f0bf7dd85 /drivers/base
parent309fe8d65034d1dd04a37f0e04d360b8764a3384 (diff)
downloadlinux-stable-579c49efdf5a04869b29891e46cde0ed4df5480a.tar.gz
linux-stable-579c49efdf5a04869b29891e46cde0ed4df5480a.tar.bz2
linux-stable-579c49efdf5a04869b29891e46cde0ed4df5480a.zip
PM / OPP: Reword binding supporting multiple regulators per device
On certain platforms (like TI), DVFS for a single device (CPU) requires configuring multiple power supplies. The OPP bindings already contains binding and example to explain this case, but it isn't sufficient. - There is no way for the code parsing these bindings to know which voltage values belong to which power supply. - It is not possible to know the order in which the supplies need to be configured while switching OPPs. This patch clarifies on those details by mentioning that such information is left for the implementation specific bindings to explain. They may want to hardcode such details or implement their own properties to get such information. All implementations using multiple regulators for their devices must provide a binding document explaining their implementation. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> Acked-by: Rob Herring <robh@kernel.org> Reviewed-by: Stephen Boyd <sboyd@codeaurora.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/base')
0 files changed, 0 insertions, 0 deletions