[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJuYYwSS0-+=D3WbwYDowZQTrFq_s1XEM_gSkgXApstPeGNWkA@mail.gmail.com>
Date: Fri, 9 Dec 2011 12:55:33 +0530
From: Thomas Abraham <thomas.abraham@...aro.org>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc: linux-kernel@...r.kernel.org, rpurdie@...ys.net,
rob.herring@...xeda.com, grant.likely@...retlab.ca,
kgene.kim@...sung.com, myungjoo.ham@...sung.com,
kyungmin.park@...sung.com, dg77.kim@...sung.com,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, Rajendra Nayak <rnayak@...com>
Subject: Re: [PATCH 2/2] regulator: add device tree support for max8997
On 9 December 2011 11:47, Mark Brown
<broonie@...nsource.wolfsonmicro.com> wrote:
> On Thu, Dec 08, 2011 at 09:57:39PM +0530, Thomas Abraham wrote:
>
>> +Required properties, if interrupts are delivered to host system:
>
> These are just optional properties, really.
Ok. Yeah, these can be classified as optional.
>
>> +- interrupt-parent: Specifies the phandle of the interrupt controller to which
>> + the interrupts from max8997 are delivered to.
>> +- interrupts: Interrupt specifiers for two interrupt sources.
>> + - First interrupt specifier is for 'irq1' interrupt.
>> + - Second interrupt specifier is for 'alert' interrupt.
>
> What if the two are connected to different interrupt controllers?
I have not thought of that. I will try to find out how to write a
device tree node for a device that delivers interrupts to separate
interrupt controllers.
Thanks,
Thomas.
>
>> + For LDO's:
>
> Extra '.
--
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/
Powered by blists - more mailing lists