linux-kernel - Re: [PATCH] irq_domain: Standardise legacy/linear domain selection

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: <20120705120215.GS4111@opensource.wolfsonmicro.com>
Date:	Thu, 5 Jul 2012 13:02:15 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Andy Shevchenko <andy.shevchenko@...il.com>
Cc:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org, mathias.nyman@...ux.intel.com,
	mika.westerberg@...ux.intel.com
Subject: Re: [PATCH] irq_domain: Standardise legacy/linear domain selection

On Thu, Jul 05, 2012 at 02:43:42PM +0300, Andy Shevchenko wrote:

> The issue is in plain array of the numbers that are assigned to the devices.
> Somehow looks better to have real namespaces, or even hide irq number in the API
> struct device, request_irq(), but keep reference between driver and PIC via some
> object.

> So, given solution just hides an issue, but doesn't resolve it fully
> from my p.o.v.

This is unrelated to what you're talking about.  The devices concerned
are mostly MFDs which use their own interrupts.  Where other things need
to use the interrupt numbers then legacy mappings should still be used
and IRQ domains have no effect at all on the situation.

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