| 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: Wed, 23 Nov 2011 09:25:36 -0800 From: Stephen Warren <swarren@...dia.com> To: Peter De Schrijver <pdeschrijver@...dia.com> CC: Russell King <linux@....linux.org.uk>, Colin Cross <ccross@...roid.com>, Olof Johansson <olof@...om.net>, Marc Dietrich <marvin24@....de>, Grant Likely <grant.likely@...retlab.ca>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>, "devicetree-discuss@...ts.ozlabs.org" <devicetree-discuss@...ts.ozlabs.org> Subject: RE: [PATCH] arm/tegra: convert tegra20 to GIC devicetree binding Peter De Schrijver wrote at Tuesday, November 22, 2011 10:00 PM: ... > I think we need to model the GPIO IRQs as a seperate interrupt controller. > That way the WM8903 node can refer to the GPIO IRQ as an IRQ without > hardcoding the global interrupt number, similar to the way we specify the > SPI number in the device nodes and not the global interrupt number. Yes, you're right. I'd originally thought that the GPIO IRQs fed directly into the GIC, but now that I read the docs, I see that the GPIO controller really is an interrupt aggregator/controller. -- nvpublic -- 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