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] [day] [month] [year] [list]
Date:	Sat, 19 May 2012 23:39:25 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] irq_domain: Standardise legacy/linear domain selection

On Sat, May 19, 2012 at 02:59:51PM -0600, Grant Likely wrote:

> It will actually be like all legacy users switched to creating an
> linear mapping, and then either associating already allocated
> irq_descs with that domain or telling the domain to pre-map a specific
> range of irq_descs (and manage allocations).  Those two use cases will
> be separate APIs.  I don't think they should be combined (at least
> from my current thinking) because it depends on whether or not the
> irq_descs are already allocated.

Hrm.  Given that the target for this API is drivers that mostly don't
care and are only supporting the current linear mappings in order to
allow their GPIOs to be used with generic drivers that only want an IRQ
I'd expect we'll wind up with a similar helper somehow.  Copying a
number around for irq_start isn't much hassle for individual drivers but
having to worry about more than that seems like too much effort, they
shouldn't have to care about the management of irq_descs.  It'd be more
work and it'd make it more painful for platforms to change between the
preallocated and dynamic models.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ