The enable GPIO is active high, but is flagged as active low in the gpio
property. As the gpio property flags are currently unused by the driver
this doesn't cause any issue for now, but will break later if the driver
starts making use of the flags. Fix it.
Signed-off-by: Laurent Pinchart <laurent.pinch...@ideasonboard.com>
---
arch/arm/boot/dts/omap4-duovero.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Cc: linux-omap@vger.kernel.org
Cc: Benoit Cousson <bcous...@baylibre.com>
Cc: Tony Lindgren <t...@atomide.com>
diff --git a/arch/arm/boot/dts/omap4-duovero.dtsi
b/arch/arm/boot/dts/omap4-duovero.dtsi
index f2a94fa62552..23c1a74f91ea 100644
--- a/arch/arm/boot/dts/omap4-duovero.dtsi
+++ b/arch/arm/boot/dts/omap4-duovero.dtsi
@@ -56,7 +56,7 @@
regulator-name = "w2cbw0015";
regulator-min-microvolt = <3000000>;
regulator-max-microvolt = <3000000>;
- gpio = <&gpio2 11 GPIO_ACTIVE_LOW>; /* gpio_43 */
+ gpio = <&gpio2 11 GPIO_ACTIVE_HIGH>; /* gpio_43 */
startup-delay-us = <70000>;
enable-active-high;
regulator-boot-on;
--
2.4.9
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
