devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: Dave Stevenson <dave.stevenson@raspberrypi.org>,
	Eric Anholt <eric@anholt.net>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Michael Zoran <mzoran@crowfest.net>,
	Baruch Siach <baruch@tkos.co.il>
Subject: [PATCH v2 2/4] dt-bindings: gpio: add raspberry pi GPIO expander binding
Date: Thu, 11 Jan 2018 21:44:25 +0200	[thread overview]
Message-ID: <a93ba9ec4d3d3ff6d1e2a79f4f813a2f86c4086b.1515698418.git.baruch@tkos.co.il> (raw)
In-Reply-To: <cover.1515698418.git.baruch@tkos.co.il>

The Raspberry Pi 3 GPIO expander is controlled by the VC4 firmware over
I2C. The firmware mailbox interface allows the ARM core to control the
GPIO lines.

Signed-off-by: Baruch Siach <baruch@tkos.co.il>
---
v2:
  * Rename compatible string to raspberrypi,firmware-gpio
---
 .../bindings/gpio/raspberrypi,firmware-gpio.txt    | 24 ++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/gpio/raspberrypi,firmware-gpio.txt

diff --git a/Documentation/devicetree/bindings/gpio/raspberrypi,firmware-gpio.txt b/Documentation/devicetree/bindings/gpio/raspberrypi,firmware-gpio.txt
new file mode 100644
index 000000000000..8faf269cf541
--- /dev/null
+++ b/Documentation/devicetree/bindings/gpio/raspberrypi,firmware-gpio.txt
@@ -0,0 +1,24 @@
+Raspberry Pi GPIO expander
+
+The Raspberry Pi 3 GPIO expander is controlled by the VC4 firmware. The
+firmware exposes a mailbox interface that allows the ARM core to control the
+GPIO lines on the expander.
+
+Required properties:
+
+- compatible : Should be "raspberrypi,firmware-gpio"
+- gpio-controller : Marks the device node as a gpio controller
+- #gpio-cells : Should be two.  The first cell is the pin number, and
+  the second cell is used to specify the gpio polarity:
+  0 = active high
+  1 = active low
+- firmware : Reference to the RPi firmware device node
+
+Example:
+
+expgpio: expgpio {
+	compatible = "raspberrypi,firmware-gpio";
+	gpio-controller;
+	#gpio-cells = <2>;
+	firmware = <&firmware>;
+};
-- 
2.15.1


  parent reply	other threads:[~2018-01-11 19:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 19:44 [PATCH v2 0/4] gpio: driver for the RPi3 GPIO expander Baruch Siach
     [not found] ` <cover.1515698418.git.baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org>
2018-01-11 19:44   ` [PATCH v2 1/4] ARM: bcm2835: sync firmware properties with downstream Baruch Siach
2018-01-13  9:57     ` Stefan Wahren
     [not found]       ` <1991337128.42939.1515837465503-7tX72C7vayboQLBSYMtkGA@public.gmane.org>
2018-01-16  9:57         ` Linus Walleij
     [not found]           ` <CACRpkdZ_g3-jR-7pOnS9MwpHprfEz8acB9SWcMLyoOVcB0iLvA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-16 10:49             ` Baruch Siach
2018-01-16 12:01               ` Stefan Wahren
2018-01-18 20:50                 ` Eric Anholt
2018-01-11 19:44 ` Baruch Siach [this message]
2018-01-13 10:06   ` [PATCH v2 2/4] dt-bindings: gpio: add raspberry pi GPIO expander binding Stefan Wahren
2018-01-11 19:44 ` [PATCH v2 3/4] gpio: raspberrypi-exp: Driver for RPi3 GPIO expander via mailbox service Baruch Siach
     [not found]   ` <35b07d1aae959c357d671f5530311320d0f10cc8.1515698418.git.baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org>
2018-01-13 10:33     ` Stefan Wahren
2018-01-13 14:49       ` Peter Robinson
2018-01-14  6:08       ` Baruch Siach
     [not found]         ` <20180114060840.ychhndc7ukulrbpe-MwjkAAnuF3khR1HGirfZ1z4kX+cae0hd@public.gmane.org>
2018-01-14 10:42           ` Stefan Wahren
2018-01-11 19:44 ` [PATCH v2 4/4] ARM: dts: bcm2837-rpi-3-b: add GPIO expander Baruch Siach
     [not found]   ` <1cb81e3d7a1b1f7ccf374952fa7e8d2147c186fb.1515698418.git.baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org>
2018-01-13 10:44     ` Stefan Wahren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a93ba9ec4d3d3ff6d1e2a79f4f813a2f86c4086b.1515698418.git.baruch@tkos.co.il \
    --to=baruch@tkos.co.il \
    --cc=dave.stevenson@raspberrypi.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eric@anholt.net \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=mzoran@crowfest.net \
    --cc=stefan.wahren@i2se.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).