Hi Linus,
hi Eric,
Am 16.01.2018 um 13:45 schrieb Baruch Siach:
Add a description of the RPi3 GPIO expander that the VC4 firmware controls.
Signed-off-by: Baruch Siach <baruch@xxxxxxxxxx>
---
v3:
* List GPIO names one per line.
v2:
* Move GPIO expander node out of the soc container
* Rename compatible string
* Add gpio-line-names property
---
arch/arm/boot/dts/bcm2837-rpi-3-b.dts | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/bcm2837-rpi-3-b.dts b/arch/arm/boot/dts/bcm2837-rpi-3-b.dts
index b44b3b5af00d..8cd93425ffe3 100644
--- a/arch/arm/boot/dts/bcm2837-rpi-3-b.dts
+++ b/arch/arm/boot/dts/bcm2837-rpi-3-b.dts
@@ -23,6 +23,22 @@
gpios = <&gpio 47 0>;
};
};
i noticed that this patch conflicts with my patch ("ARM: dts: bcm283x:
Use GPIO polarity defines consistently") in linux-next.
How should we proceed?
+
+ expgpio: gpio-expander {
+ compatible = "raspberrypi,firmware-gpio";
+ gpio-controller;
+ #gpio-cells = <2>;
+ firmware = <&firmware>;
+ gpio-line-names = "BT_ON",
+ "WL_ON",
+ "STATUS_LED",
+ "LAN_RUN",
+ "HPD_N",
+ "CAM_GPIO0",
+ "CAM_GPIO1",
+ "PWR_LOW_N";
+ status = "okay";
+ };
};
/* uart0 communicates with the BT module */
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
