[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1381487207-18298-1-git-send-email-nm@ti.com>
Date: Fri, 11 Oct 2013 05:26:47 -0500
From: Nishanth Menon <nm@...com>
To: Rob Landley <rob@...dley.net>, Mark Brown <broonie@...aro.org>
CC: Rob Herring <rob.herring@...xeda.com>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Stephen Warren <swarren@...dotorg.org>,
Kishon Vijay Abraham I <kishon@...com>,
<devicetree@...r.kernel.org>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Rajendra Nayak <rnayak@...com>,
Nishanth Menon <nm@...com>
Subject: [PATCH] regulator: dts: Fix bindings description of regulator-boot-on
Since regulator-boot-on property maps back to constraints->boot_on,
current description of 'regulator-boot-on' property conflicts with
description of 'boot-on' in include/linux/regulator/machine.h and the
corresponding implementation in drivers/regulator/core.c.
Ensure the description is more inline with the original intent.
Cc: Rajendra Nayak <rnayak@...com>
Reported-by: Kishon Vijay Abraham I <kishon@...com>
Signed-off-by: Nishanth Menon <nm@...com>
---
Ref: my confusion in http://marc.info/?t=138140228800004&r=1&w=2
Based on v3.12-rc4 tag
.../devicetree/bindings/regulator/regulator.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/regulator/regulator.txt b/Documentation/devicetree/bindings/regulator/regulator.txt
index 2bd8f09..d999f096 100644
--- a/Documentation/devicetree/bindings/regulator/regulator.txt
+++ b/Documentation/devicetree/bindings/regulator/regulator.txt
@@ -8,7 +8,9 @@ Optional properties:
- regulator-min-microamp: smallest current consumers may set
- regulator-max-microamp: largest current consumers may set
- regulator-always-on: boolean, regulator should never be disabled
-- regulator-boot-on: bootloader/firmware enabled regulator
+- regulator-boot-on: regulator is enabled when the system is initially started.
+ If the regulator is not enabled by the hardware or bootloader then it will be
+ enabled when the constraints are applied.
- regulator-allow-bypass: allow the regulator to go into bypass mode
- <name>-supply: phandle to the parent supply/regulator node
- regulator-ramp-delay: ramp delay for regulator(in uV/uS)
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists