On Fri, Jul 20, 2018 at 04:16:05PM +0530, Vijay Viswanath wrote:
The load a particular sdhc controller should request from a regulator
is device specific and hence each device should individually vote for
the required load.
"dt-bindings: mmc: ..." for the subject.
quoted hunk ↗ jump to hunk
Signed-off-by: Vijay Viswanath <redacted>
---
Documentation/devicetree/bindings/mmc/sdhci-msm.txt | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/sdhci-msm.txt b/Documentation/devicetree/bindings/mmc/sdhci-msm.txt
index 502b3b8..ee34f28 100644
--- a/Documentation/devicetree/bindings/mmc/sdhci-msm.txt
+++ b/Documentation/devicetree/bindings/mmc/sdhci-msm.txt
@@ -26,6 +26,11 @@ Required properties:
"cal" - reference clock for RCLK delay calibration (optional)
"sleep" - sleep clock for RCLK delay calibration (optional)
+Optional properties:
+- <supply>-current-level - specifies load levels for supply during BUS_ON
+ and BUS_OFF states in power irq. Should be specified in
+ pairs (lpm, hpm), for BUS_OFF and BUS_ON respectively.
+ Units uA.
This should probably be a common regulator property (or maybe one exists
already).
It is missing vendor prefix and unit suffix as-is.
Rob