| 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
| ||
|
Message-ID: <20111209063912.GG26952@opensource.wolfsonmicro.com> Date: Fri, 9 Dec 2011 14:39:13 +0800 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: Thomas Abraham <thomas.abraham@...aro.org> Cc: linux-kernel@...r.kernel.org, rpurdie@...ys.net, rob.herring@...xeda.com, grant.likely@...retlab.ca, kgene.kim@...sung.com, myungjoo.ham@...sung.com, kyungmin.park@...sung.com, dg77.kim@...sung.com, linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org Subject: Re: [PATCH 1/2] mfd: add irq domain support for max8997 interrupts On Fri, Dec 09, 2011 at 12:00:07PM +0530, Thomas Abraham wrote: > If these gpio's are connected to the host system, and host system sets > up gpio interrupt notification for these gpio lines, the linux irq > number for the gpio interrupt would belong to the irq domain of the > host interrupt controller (gic irq domain in case of exynos). > Consumers of this interrupt would use the gpio interrupt independent > of the max8997 irq domain. So irq_base can be maintained private to > the max8997 mfd driver and its sub-block drivers. How would you provide this interrupt to the device using it in a non-DT systemm without passing the irq_base into the device as platform data? -- 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