linux-kernel - Re: [PATCH 03/03] GPIO: Add TB10x GPIO driver

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: <C89F2E38-4428-4AA9-B032-630F3BEA4C1D@codeaurora.org>
Date:	Thu, 24 Oct 2013 22:27:43 -0500
From:	Kumar Gala <galak@...eaurora.org>
To:	Christian Ruppert <christian.ruppert@...lis.com>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	Stephen Warren <swarren@...dotorg.org>,
	Patrice CHOTARD <patrice.chotard@...com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	Rob Herring <rob.herring@...xeda.com>,
	Rob Landley <rob@...dley.net>,
	Sascha Leuenberger <sascha.leuenberger@...lis.com>,
	Pierrick Hascoet <pierrick.hascoet@...lis.com>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	Alexandre Courbot <acourbot@...dia.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH 03/03] GPIO: Add TB10x GPIO driver


On Oct 8, 2013, at 7:25 AM, Christian Ruppert wrote:

> The GPIO driver for the Abilis Systems TB10x series of SOCs based on ARC700
> CPUs. It supports GPIO control and GPIO interrupt generation. This driver
> works in conjunction with the TB10x pinctrl driver.
> 
> Signed-off-by: Sascha Leuenberger <sascha.leuenberger@...lis.com>
> Signed-off-by: Christian Ruppert <christian.ruppert@...lis.com>
> ---
> .../devicetree/bindings/gpio/abilis,tb10x-gpio.txt |   36 ++
> drivers/gpio/Kconfig                               |    4 +
> drivers/gpio/Makefile                              |    1 +
> drivers/gpio/gpio-tb10x.c                          |  341 ++++++++++++++++++++
> 4 files changed, 382 insertions(+), 0 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/gpio/abilis,tb10x-gpio.txt
> create mode 100644 drivers/gpio/gpio-tb10x.c
> 
> diff --git a/Documentation/devicetree/bindings/gpio/abilis,tb10x-gpio.txt b/Documentation/devicetree/bindings/gpio/abilis,tb10x-gpio.txt
> new file mode 100644
> index 0000000..00611ac
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/gpio/abilis,tb10x-gpio.txt
> @@ -0,0 +1,36 @@
> +* Abilis TB10x GPIO controller
> +
> +Required Properties:
> +- compatible: Should be "abilis,tb10x-gpio"
> +- reg: Address and length of the register set for the device
> +- gpio-controller: Marks the device node as a gpio controller.
> +- #gpio-cells: Should be <2>. The first cell is the pin number and the
> +  second cell is used to specify optional parameters:
> +   - bit 0 specifies polarity (0 for normal, 1 for inverted).
> +- abilis,ngpio: the number of GPIO pins this driver controls.
> +
> +Optional Properties:
> +- interrupt-controller: Marks the device node as an interrupt controller.
> +- #interrupt-cells: Should be <1>. Interrupts are triggered on both edges.
> +- interrupts: Defines the interrupt line connecting this GPIO controller to
> +  its parent interrupt controller.
> +- interrupt-parent: Defines the parent interrupt controller.
> +
> +GPIO ranges are specified as described in
> +Documentation/devicetree/bindings/gpio/gpio.txt
> +
> +Example:
> +
> +	gpioa: gpio@...40000 {
> +		compatible = "abilis,tb10x-gpio";
> +		interrupt-controller;
> +		#interrupt-cells = <1>;
> +		interrupt-parent = <&tb10x_ictl>;
> +		interrupts = <27 2>;
> +		reg = <0xFF140000 0x1000>;
> +		gpio-controller;
> +		#gpio-cells = <2>;
> +		abilis,ngpio = <3>;
> +		gpio-ranges = <&iomux 0 0 0>;
> +		gpio-ranges-group-names = "gpioa_pins";
> +	};

For the Binding part:

Acked-by: Kumar Gala <galak@...eaurora.org>

- k

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/