[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180318125304.3i3kqzcefhv5iusv@rob-hp-laptop>
Date: Sun, 18 Mar 2018 07:53:04 -0500
From: Rob Herring <robh@...nel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc: linus.walleij@...aro.org, afaerber@...e.de,
liuwei@...ions-semi.com, mp-cs@...ions-semi.com,
96boards@...obotics.com, devicetree@...r.kernel.org,
andy.shevchenko@...il.com, daniel.thompson@...aro.org,
amit.kucheria@...aro.org, linux-arm-kernel@...ts.infradead.org,
linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
hzhang@...obotics.com, bdong@...obotics.com,
manivannanece23@...il.com
Subject: Re: [PATCH v5 4/9] dt-bindings: gpio: Add gpio nodes for Actions
S900 SoC
On Fri, Mar 09, 2018 at 10:43:40AM +0530, Manivannan Sadhasivam wrote:
> Add gpio nodes for Actions Semi S900 SoC.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
> ---
> .../devicetree/bindings/gpio/actions,owl-gpio.txt | 90 ++++++++++++++++++++++
> 1 file changed, 90 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/gpio/actions,owl-gpio.txt
>
> diff --git a/Documentation/devicetree/bindings/gpio/actions,owl-gpio.txt b/Documentation/devicetree/bindings/gpio/actions,owl-gpio.txt
> new file mode 100644
> index 000000000000..ad7d32ce2abe
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/gpio/actions,owl-gpio.txt
> @@ -0,0 +1,90 @@
> +* Actions Semi OWL GPIO controller bindings
> +
> +The GPIOs are organized as individual banks/ports with variable number
> +of GPIOs. Each bank is represented as an individual GPIO controller.
> +
> +Required properties:
> +- compatible : Should be "actions,s900-gpio"
> +- reg : Address and range of the GPIO controller registers.
> +- gpio-controller : Marks the device node as a GPIO controller.
> +- #gpio-cells : Should be <2>. The first cell is the gpio number
> + and the second cell is used to specify optional
> + parameters.
> +- ngpios : Specifies the number of GPIO lines.
> +- interrupt-controller : Marks the device node as an interrupt controller.
> +- #interrupt-cells : Specifies the number of cells needed to encode an
> + interrupt. Shall be set to 2. The first cell
> + defines the interrupt number, the second encodes
> + the trigger flags described in
> + bindings/interrupt-controller/interrupts.txt
> +
> +Optional properties:
> +- gpio-ranges : Mapping between GPIO and pinctrl
> +
> +Examples:
> +
> + gpioa: gpio@...b0000 {
> + compatible = "actions,s900-gpio";
> + reg = <0x0 0xe01b0000 0x0 0x1000>;
> + gpio-controller;
> + #gpio-cells = <2>;
> + gpio-ranges = <&pinctrl 0 0 32>;
> + ngpios = <32>;
This is only needed if the number of gpios is reduced for some reason
such as not pinned out. IOW, 32 is implied because that's the size of
each bank.
> + interrupt-controller;
> + #interrupt-cells = <2>;
> + };
> +
> + gpiob: gpio@...b000c {
> + compatible = "actions,s900-gpio";
> + reg = <0x0 0xe01b000c 0x0 0x1000>;
Due to the sizes, these are still overlapping.
Rob
> + gpio-controller;
> + #gpio-cells = <2>;
> + gpio-ranges = <&pinctrl 0 32 32>;
> + ngpios = <32>;
> + interrupt-controller;
> + #interrupt-cells = <2>;
> + };
Powered by blists - more mailing lists