From: Rob Herring <robh@kernel.org>
To: Andrei.Stefanescu@microchip.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
gregkh@linuxfoundation.org, linus.walleij@linaro.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Ludovic.Desroches@microchip.com,
linux-arm-kernel@lists.infradead.org,
Cristian.Birsan@microchip.com
Subject: Re: [PATCH 1/3] dt-bindings: gpio: add sama5d2 PIOBU support
Date: Mon, 12 Nov 2018 12:57:33 -0600 [thread overview]
Message-ID: <5bea0ec9.1c69fb81.db750.9b4e@mx.google.com> (raw)
In-Reply-To: <1541603580-17448-2-git-send-email-andrei.stefanescu@microchip.com>
On Wed, Nov 07, 2018 at 03:12:32PM +0000, Andrei.Stefanescu@microchip.com wrote:
> This patch describes the compatible and the device tree
> bindings necessary for the sama5d2 PIOBU GPIO
> controller driver.
Bindings describe the h/w, not drivers.
>
> Signed-off-by: Andrei Stefanescu <andrei.stefanescu@microchip.com>
> ---
> .../bindings/gpio/gpio-sama5d2-piobu.txt | 23 ++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/gpio/gpio-sama5d2-piobu.txt
>
> diff --git a/Documentation/devicetree/bindings/gpio/gpio-sama5d2-piobu.txt b/Documentation/devicetree/bindings/gpio/gpio-sama5d2-piobu.txt
> new file mode 100644
> index 0000000..791ac51
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/gpio/gpio-sama5d2-piobu.txt
> @@ -0,0 +1,23 @@
> +GPIO controller for SAMA5D2 PIOBU pins.
> +
> +This pins have the property of not losing their voltage
> +during Backup/Self-refresh mode.
> +
> +These bindings should be set to a node in the dtsi file.
> +
> +Required properties:
> +- compatible: "syscon", "microchip,sama5d2-piobu"
Why the syscon?
syscon should be last if it remains.
> +- #gpio-cells: There are 2. The pin number is the
> + first, the second represents additional
> + parameters such as GPIO_ACTIVE_HIGH/LOW.
> +- gpio-controller: Marks the port as GPIO controller.
No interrupt capability?
> +
> +Example:
> +
> + secumod@fc040000 {
gpio@...
> + compatible = "syscon", "microchip,sama5d2-piobu";
> + reg = <0xfc040000 0x100>;
> +
> + gpio-controller;
> + #gpio-cells = <2>;
> + };
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-11-12 18:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 15:12 [PATCH 0/3] add sama5d2 PIOBU GPIO driver Andrei.Stefanescu
2018-11-07 15:12 ` [PATCH 1/3] dt-bindings: gpio: add sama5d2 PIOBU support Andrei.Stefanescu
2018-11-12 18:57 ` Rob Herring [this message]
2018-11-15 9:43 ` Linus Walleij
2018-11-07 15:12 ` [PATCH 2/3] MAINTAINERS: add maintainer for sama5d2 PIOBU GPIO driver Andrei.Stefanescu
2018-11-15 9:40 ` Linus Walleij
2018-11-07 15:12 ` [PATCH 3/3] gpio: add driver for sama5d2 PIOBU pins Andrei.Stefanescu
2018-11-15 9:56 ` Linus Walleij
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=5bea0ec9.1c69fb81.db750.9b4e@mx.google.com \
--to=robh@kernel.org \
--cc=Andrei.Stefanescu@microchip.com \
--cc=Cristian.Birsan@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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).