Re: [PATCH v2 1/7] dt-binding: Add ngpios property to GPIO controller node

From: Rob Herring
Date: Fri Nov 20 2015 - 10:33:27 EST


On Thu, Nov 19, 2015 at 09:22:13AM +0530, Pramod Kumar wrote:
> Add ngpios property to the gpio controller's DT node so that controller
> driver extracts total number of in-use gpio lines from DT and removes
> dependency on driver.
>
> Signed-off-by: Pramod Kumar <pramodku@xxxxxxxxxxxx>
> Reviewed-by: Ray Jui <rjui@xxxxxxxxxxxx>
> Reviewed-by: Scott Branden <sbranden@xxxxxxxxxxxx>

Acked-by: Rob Herring <robh@xxxxxxxxxx>

> ---
> Documentation/devicetree/bindings/pinctrl/brcm,cygnus-gpio.txt | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/brcm,cygnus-gpio.txt b/Documentation/devicetree/bindings/pinctrl/brcm,cygnus-gpio.txt
> index 16589fb6..8b1e5d1 100644
> --- a/Documentation/devicetree/bindings/pinctrl/brcm,cygnus-gpio.txt
> +++ b/Documentation/devicetree/bindings/pinctrl/brcm,cygnus-gpio.txt
> @@ -10,6 +10,9 @@ Required properties:
> Define the base and range of the I/O address space that contains the Cygnus
> GPIO/PINCONF controller registers
>
> +- ngpios:
> + Total number of in-use slots in GPIO controller
> +
> - #gpio-cells:
> Must be two. The first cell is the GPIO pin number (within the
> controller's pin space) and the second cell is used for the following:
> @@ -57,6 +60,7 @@ Example:
> compatible = "brcm,cygnus-ccm-gpio";
> reg = <0x1800a000 0x50>,
> <0x0301d164 0x20>;
> + ngpios = <24>;
> #gpio-cells = <2>;
> gpio-controller;
> interrupts = <GIC_SPI 84 IRQ_TYPE_LEVEL_HIGH>;
> @@ -78,6 +82,7 @@ Example:
> gpio_asiu: gpio@180a5000 {
> compatible = "brcm,cygnus-asiu-gpio";
> reg = <0x180a5000 0x668>;
> + ngpios = <146>;
> #gpio-cells = <2>;
> gpio-controller;
> interrupts = <GIC_SPI 174 IRQ_TYPE_LEVEL_HIGH>;
> --
> 1.9.1
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/