From: thomas.abraham@linaro.org (Thomas Abraham)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] regulator: add device tree support for max8997
Date: Fri, 9 Dec 2011 12:55:33 +0530 [thread overview]
Message-ID: <CAJuYYwSS0-+=D3WbwYDowZQTrFq_s1XEM_gSkgXApstPeGNWkA@mail.gmail.com> (raw)
In-Reply-To: <20111209061720.GF26952@opensource.wolfsonmicro.com>
On 9 December 2011 11:47, Mark Brown
<broonie@opensource.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 '.
next prev parent reply other threads:[~2011-12-09 7:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 16:27 [PATCH 0/2] Add device tree support for MAX8997 Thomas Abraham
2011-12-08 16:27 ` [PATCH 1/2] mfd: add irq domain support for max8997 interrupts Thomas Abraham
2011-12-08 16:27 ` [PATCH 2/2] regulator: add device tree support for max8997 Thomas Abraham
2011-12-09 2:30 ` Kyungmin Park
2011-12-09 5:17 ` Thomas Abraham
2011-12-09 6:17 ` Mark Brown
2011-12-09 7:25 ` Thomas Abraham [this message]
2011-12-09 4:00 ` [PATCH 1/2] mfd: add irq domain support for max8997 interrupts MyungJoo Ham
2011-12-09 4:41 ` Mark Brown
2011-12-09 5:25 ` Thomas Abraham
2011-12-09 6:02 ` Mark Brown
2011-12-09 6:30 ` Thomas Abraham
2011-12-09 6:39 ` Mark Brown
2011-12-09 7:19 ` Thomas Abraham
2011-12-09 8:15 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJuYYwSS0-+=D3WbwYDowZQTrFq_s1XEM_gSkgXApstPeGNWkA@mail.gmail.com' \
--to=thomas.abraham@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).