The Cirrus Logic Madera codecs have a range of GPIO pins that can be
used as single-bit logic input or output. These are presented as a
standard GPIO binding.

The second cell in a GPIO binding is currently reserved for future use
as chip-specific flags.

Signed-off-by: Richard Fitzgerald <[email protected]>
---
Changes from V1:
- moved out of main gpio patch into a separate patch
- added gpio-line-names as an optional property

 .../devicetree/bindings/gpio/gpio-madera.txt       | 27 ++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/gpio/gpio-madera.txt

diff --git a/Documentation/devicetree/bindings/gpio/gpio-madera.txt 
b/Documentation/devicetree/bindings/gpio/gpio-madera.txt
new file mode 100644
index 0000000..6254f5b
--- /dev/null
+++ b/Documentation/devicetree/bindings/gpio/gpio-madera.txt
@@ -0,0 +1,27 @@
+Cirrus Logic Madera class audio codecs gpio driver
+
+This is a subnode of the parent mfd node.
+
+See also the core bindings for the parent MFD driver:
+See Documentation/devicetree/bindings/mfd/madera.txt
+
+Required properties:
+  - compatible : must be "cirrus,madera-gpio"
+  - gpio-controller : Indicates this device is a GPIO controller.
+  - #gpio-cells : Must be 2. The first cell is the pin number. The second cell
+    is reserved for future use and must be zero
+
+Optional properties:
+  - gpio-line-names : as described in bindings/gpio/gpio.txt
+
+Example:
+
+cs47l85@0 {
+       compatible = "cirrus,cs47l85";
+
+       gpio {
+               compatible = "cirrus,madera-gpio";
+               gpio-controller;
+               #gpio-cells = <2>;
+       }
+};
-- 
1.9.1

Reply via email to