[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130618180707.GO1403@sirena.org.uk>
Date: Tue, 18 Jun 2013 19:07:07 +0100
From: Mark Brown <broonie@...nel.org>
To: Stephen Warren <swarren@...dotorg.org>
Cc: "J, KEERTHY" <j-keerthy@...com>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
"ldewangan@...dia.com" <ldewangan@...dia.com>,
"sameo@...ux.intel.com" <sameo@...ux.intel.com>,
"grant.likely@...retlab.ca" <grant.likely@...retlab.ca>,
"swarren@...dia.com" <swarren@...dia.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"gg@...mlogic.co.uk" <gg@...mlogic.co.uk>
Subject: Re: [PATCH v2 1/4] MFD: Palmas: Check if interrupts property exists
and then only request irq
On Tue, Jun 18, 2013 at 11:22:41AM -0600, Stephen Warren wrote:
> If the device was instantiated from a board file *or* a device tree,
> i2c->irq is correctly set. Hence, checking that value works in both cases.
The same thing will happen with any other firmware interface that gets
introduced in the future - one of the goals with factoring all this out
into the bus code is that it means the driver doesn't need to have any
special handling.
> If you check the interrupts DT property, that will only work if the
> device was instantiated from device tree, and not if it was instantiated
> from a board file; the property will never exist in the board file case,
> and hence you'll never be able to have a board file provide an interrupt.
Exactly.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists