linux-kernel - Re: [PATCH 02/11] GPIO: DA9052 GPIO module v3

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:	Wed, 6 Jul 2011 15:44:42 -0700
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	ashishj3 <ashish.jangam@...tcummins.com>, grant@...retlab.ca,
	arnd@...db.de, jic23@....ac.uk, linux-kernel@...r.kernel.org,
	Dajun <dajun.chen@...semi.com>, linaro-dev@...ts.linaro.org
Subject: Re: [PATCH 02/11] GPIO: DA9052 GPIO module v3

On Wed, Jul 06, 2011 at 10:36:56AM -0600, Grant Likely wrote:

> It looks like this needs to be merged via the MFD tree since it
> depends on the core da9052 driver patch.

Actually that's not such an issue for new MFDs - since the function
drivers all depend on the core driver they can't be enabled in Kconfig
until the MFD part has been merged so don't do any harm.

> > +static int da9052_gpio_to_irq(struct gpio_chip *gc, u32 offset)
> > +{
> > +	struct da9052_gpio *gpio = to_da9052_gpio(gc);
> > +	struct da9052 *da9052 = gpio->da9052;

> > +	return da9052->irq_base + DA9052_IRQ_GPI0 + offset;

> Who allocates the irq_descs for these irqs?

SoP for MFDs is to do this in the core as part of the larger block of
interrupts, the core driver is doing this.
--
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/