linux-kernel - Re: [PATCH v9] gpio: add a driver for Synopsys DesignWare APB 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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 17 Dec 2013 11:50:09 -0600
From:	delicious quinoa <delicious.quinoa@...il.com>
To:	Steffen Trumtrar <s.trumtrar@...gutronix.de>
Cc:	Linus Walleij <linus.walleij@...ricsson.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	Jamie Iles <jamie@...ieiles.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	Rob Herring <rob.herring@...xeda.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
	Heiko Stuebner <heiko@...ech.de>, Alan Tull <atull@...era.com>,
	Dinh Nguyen <dinguyen@...era.com>,
	Yves Vandervennet <rocket.yvanderv@...il.com>
Subject: Re: [PATCH v9] gpio: add a driver for Synopsys DesignWare APB GPIO

On Thu, Dec 12, 2013 at 3:08 AM, Steffen Trumtrar
<s.trumtrar@...gutronix.de> wrote:
> Sorry for chiming in late. I tested your driver on the Sockit and the GPIOs
> work fine (basically just tested the 4 HPS LEDS that are on this board).
>
> With the interrupt support I had a little trouble though:
> The Sockit has an ADXL345 on the i2c bus with a gpio as interrupt line.
>
> First: When you use "interrupt-parent", you have to specify the gpio node,
> rather than the gpio-bank that has the interrupt-controller property. Is
> that expected? I'm not really sure if that is normal behavior...

I think it can work several ways.  In my device tree, the gic is one
level up in the device tree above the gpio.  So I don't have to
specify interrupt-controller in the gpio node or in the bank.

>
> Second: The interrupt is registered as "GIC 37", which is a real interrupt on
> the Socfpga. I would expect it to be marked as "GPIO 2xx" (or something in that
> range). The interrupt from the gpiochip itself isn't registered at all ?!

The bindings documentation is an example.  You will need to adjust the
device tree bindings values to suit your board.  For example, on my
socfpga cyclone5 board, I needed:

        gpio0: gpio@...08000 {
                compatible = "snps,dw-apb-gpio";
                reg = <0xff708000 0x1000>;
                #address-cells = <1>;
                #size-cells = <0>;

                port0a: gpio-controller@0 {
                        compatible = "snps,dw-apb-gpio-port";
                        gpio-controller;
                        #gpio-cells = <2>;
                        snps,nr-gpios = <29>;
                        reg = <0>;
                        interrupt-controller;
                        interrupts = <0 164 4>;
                        #interrupt-cells = <2>;
                        clocks = <&per_base_clk>;
                        };
                };

(so on for gpio1 and gpio2)

>
> Third: The interrupt didn't work. But that might also be my failure. I guess/hope
> you tested interrupts successfully?!

Yes, tested and working for me, including the interrupts.

>
> (Fourth: small typo in the documentation example: "snps,nr-gpio" instead of "snps,nr-gpios")

Yes, should be the plural form.

Thanks for testing!

Alan

>
> Regards,
> Steffen
>
>
> --
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
--
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/