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
| ||
|
Date: Tue, 24 Sep 2013 10:59:07 -0600 From: Stephen Warren <swarren@...dotorg.org> To: Linus Walleij <linus.walleij@...aro.org> CC: Lars Poeschel <poeschel@...onage.de>, Javier Martinez Canillas <javier.martinez@...labora.co.uk>, Mark Brown <broonie@...nel.org>, Lars Poeschel <larsi@....tu-dresden.de>, Grant Likely <grant.likely@...aro.org>, "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, Mark Rutland <mark.rutland@....com>, Ian Campbell <ian.campbell@...rix.com>, Kumar Gala <galak@...eaurora.org>, Pawel Moll <pawel.moll@....com>, Tomasz Figa <tomasz.figa@...il.com>, Enric Balletbo i Serra <eballetbo@...il.com>, Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>, Santosh Shilimkar <santosh.shilimkar@...com>, Kevin Hilman <khilman@...aro.org>, Balaji T K <balajitk@...com>, Tony Lindgren <tony@...mide.com>, Jon Hunter <jgchunter@...il.com>, joelf@...com, Laurent Pinchart <laurent.pinchart+renesas@...asonboard.com> Subject: Re: [PATCH v3] gpio: interrupt consistency check for OF GPIO IRQs On 09/24/2013 02:31 AM, Linus Walleij wrote: > On Mon, Sep 23, 2013 at 10:21 PM, Stephen Warren <swarren@...dotorg.org> wrote: ... >> Perhaps rather than having the gpio_chip/irq_chip drivers physically >> implement a function which calls this common code, they could set some >> flags/data/... in the struct gpio_chip/irq_chip indicating that they >> desire the core code that implements the error-checking to be enabled. > > I think it should more be like a function they can call to flag > a GPIO as used for IRQ. For the record, that's pretty much exactly what I meant by implementing it in the drivers. The irq_chip driver knows when the IRQ has been requested, and calls some gpiolib function to mark the GPIO as in-use-as-an-IRQ. -- 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/
Powered by blists - more mailing lists