linux-kernel - Re: [PATCH 1/2] gpio: mmio: add support for NI 169445 NAND GPIO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4019620.oLiLCkQLlD@debian64>
Date:   Fri, 10 Mar 2017 11:21:14 +0100
From:   Christian Lamparter <chunkeey@...glemail.com>
To:     Nathan Sullivan <nathan.sullivan@...com>
Cc:     linus.walleij@...aro.org, gnurou@...il.com, mark.rutland@....com,
        devicetree@...r.kernel.org, robh+dt@...nel.org,
        ralf@...ux-mips.org, linux-kernel@...r.kernel.org,
        linux-gpio@...r.kernel.org, linux-mips@...ux-mips.org
Subject: Re: [PATCH 1/2] gpio: mmio: add support for NI 169445 NAND GPIO

On Wednesday, March 8, 2017 1:35:43 PM CET Nathan Sullivan wrote:
> The GPIO-based NAND controller on National Instruments 169445 hardware
> exposes a set of simple lines for the control signals.
> 
> Signed-off-by: Nathan Sullivan <nathan.sullivan@...com>
> ---
>  .../bindings/gpio/ni,169445-nand-gpio.txt          | 36 ++++++++++++++++++++++
>  drivers/gpio/gpio-mmio.c                           |  1 +
>  2 files changed, 37 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/gpio/ni,169445-nand-gpio.txt
> 
> diff --git a/Documentation/devicetree/bindings/gpio/ni,169445-nand-gpio.txt b/Documentation/devicetree/bindings/gpio/ni,169445-nand-gpio.txt
> new file mode 100644
> index 0000000..ca2c14f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/gpio/ni,169445-nand-gpio.txt
> @@ -0,0 +1,36 @@
> +Bindings for the National Instruments 169445 GPIO NAND controller
> +
> +The 169445 GPIO NAND controller has two memory mapped GPIO registers, one
> +for input (the ready signal) and one for output (control signals).  It is
> +intended to be used with the GPIO NAND driver.
> +
> +Required properties:
> +	- compatible: should be "ni,169445-nand-gpio"
> +	- reg-names: must contain
> +		"dat" - data register
> +	- reg: address + size pairs describing the GPIO register sets;
> +		order must correspond with the order of entries in reg-names
> +	- #gpio-cells: must be set to 2. The first cell is the pin number and
> +			the second cell is used to specify the gpio polarity:
> +			0 = active high
> +			1 = active low
> +	- gpio-controller: Marks the device node as a gpio controller.
> +
> +Examples:
> +	gpio1: nand-gpio-out@...00010 {
> +		compatible = "ni,169445-nand-gpio";
> +		reg = <0x1f300010 0x4>;
> +		reg-names = "dat";
> +		gpio-controller;
> +		#gpio-cells = <2>;
> +		ngpios = <5>;
ngpios? Where is this parameter parsed? Is there a description for it
in the Documentation?

> +	};
> +
> +	gpio2: nand-gpio-in@...00014 {
^^ I assume this GPIO only has input? Is this right?
If so you can specify the following dt property:

	no-output;

So, all gpios can only be inputs.

> +		compatible = "ni,169445-nand-gpio";
> +		reg = <0x1f300014 0x4>;
> +		reg-names = "dat";
> +		gpio-controller;
> +		#gpio-cells = <2>;
> +		ngpios = <1>;
Same as above.

I think you should could either add a parser for the ngpios property.
by adding of_property_read_u16(&pdev->dev, "ngpios", &gc->ngpio);
in the right place. or remove the property.

> +	};
> diff --git a/drivers/gpio/gpio-mmio.c b/drivers/gpio/gpio-mmio.c
> index d7d03ad..f7da40e 100644
> --- a/drivers/gpio/gpio-mmio.c
> +++ b/drivers/gpio/gpio-mmio.c
> @@ -575,6 +575,7 @@ static void __iomem *bgpio_map(struct platform_device *pdev,
>  static const struct of_device_id bgpio_of_match[] = {
>  	{ .compatible = "brcm,bcm6345-gpio" },
>  	{ .compatible = "wd,mbl-gpio" },
> +	{ .compatible = "ni,169445-nand-gpio" },
Maybe you could add this entry above the wd,mbl-gpio. 
So it's in alphabetical order. That's said, it's fine
the way it is.

>  	{ }
>  };
>  MODULE_DEVICE_TABLE(of, bgpio_of_match);
>