linux-kernel - Re: How to create IRQ mappings in a GPIO driver that doesn't control its IRQ domain ?

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: <20130725131556.GD9858@sirena.org.uk>
Date:	Thu, 25 Jul 2013 14:15:56 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	Grant Likely <grant.likely@...aro.org>,
	Guennadi Liakhovetski <g.liakhovetski@....de>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: How to create IRQ mappings in a GPIO driver that doesn't control
 its IRQ domain ?

On Thu, Jul 25, 2013 at 11:45:33AM +0200, Laurent Pinchart wrote:

> The two devices are independent, so there's no real parent/child relationship. 
> However, as Grant proposed, I could list all the interrupts associated with 
> GPIOs in the GPIO controller DT node. I would then just call 
> irq_of_parse_and_map() in the .to_irq() handler to magically translate the 
> GPIO number to a mapped IRQ number.

> The number of interrupts can be pretty high (up to 58 in the worst case so 
> far), so an alternative would be to specify the interrupt-parent only, and 
> call irq_create_of_mapping() directly. What solution would you prefer ?

Are the interrupts in a contiguous block in the controller so you can
just pass around the controller and a base number?

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)