From: Scott Wood <scottwood@freescale.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Detlev Zundel <dzu@denx.de>,
Markus Fischer <markus.fischer.ec@ifm.com>,
devicetree-discuss@lists.ozlabs.org,
Michael Weiss <michael.weiss@ifm.com>,
linuxppc-dev@ozlabs.org, Anatolij Gustschin <agust@denx.de>,
Wolfgang Grandegger <wg@denx.de>
Subject: Re: [PATCH 2/2] powerpc/mpc5121: add initial support for PDM360NG board
Date: Wed, 19 May 2010 16:37:35 -0500 [thread overview]
Message-ID: <4BF45A1F.70100@freescale.com> (raw)
In-Reply-To: <AANLkTilBveOR1aJTgunOq0aqnsGtf1vWHfn8A6uXyoPU@mail.gmail.com>
On 05/19/2010 04:27 PM, Grant Likely wrote:
> On Mon, May 3, 2010 at 10:34 AM, Scott Wood<scottwood@freescale.com> wrote:
>> Grant Likely wrote:
>>>>
>>>> + // IPIC
>>>> + // interrupts cell =<intr #, sense>
>>>> + // sense values match linux IORESOURCE_IRQ_* defines:
>>>> + // sense == 8: Level, low assertion
>>>> + // sense == 2: Edge, high-to-low change
>>>> + //
>>>> + ipic: interrupt-controller@c00 {
>>>> + compatible = "fsl,mpc5121-ipic", "fsl,ipic";
>>>> + interrupt-controller;
>>>> + #address-cells =<0>;
>>>
>>> Don't need #address-cells here
>>
>> #address-cells is required by ePAPR for interrupt controllers if an
>> interrupt-map is used.
>
> Why?
>
> /me is too lazy to dig out ePAPR and look.
Address cells are part of the interrupt identification. Typically with
interrupt maps this is only used on the child end (e.g. to select a
particular PCI slot), but if the parent interrupt controller's address
cells are non-zero it will be expected in the parent interrupt specifier
as well.
I believe the only part of this that is new with ePAPR is that it asks
that the interrupt controller address cells be explicitly specified, as
it's a bit icky for it to default to 2 in some contexts and 0 in others.
-Scott
next prev parent reply other threads:[~2010-05-19 21:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 20:30 [PATCH 1/2] powerpc/mpc512x: Group mpc512x board's selection menu Anatolij Gustschin
2010-04-30 20:30 ` [PATCH 2/2] powerpc/mpc5121: add initial support for PDM360NG board Anatolij Gustschin
2010-05-02 14:54 ` Grant Likely
2010-05-03 9:22 ` Anatolij Gustschin
2010-05-03 16:34 ` Scott Wood
2010-05-19 21:27 ` Grant Likely
2010-05-19 21:37 ` Scott Wood [this message]
2010-05-19 21:47 ` Grant Likely
2010-06-22 21:39 ` Scott Wood
2010-05-03 10:23 ` [PATCH v2 " Anatolij Gustschin
2010-07-23 13:49 ` [PATCH v3 " Anatolij Gustschin
2010-07-25 7:42 ` Grant Likely
2010-07-27 10:36 ` Anatolij Gustschin
2010-07-27 16:58 ` Grant Likely
2010-07-27 17:28 ` Anatolij Gustschin
2010-07-27 17:43 ` Grant Likely
2010-07-27 21:26 ` [PATCH v4 " Anatolij Gustschin
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=4BF45A1F.70100@freescale.com \
--to=scottwood@freescale.com \
--cc=agust@denx.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dzu@denx.de \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=markus.fischer.ec@ifm.com \
--cc=michael.weiss@ifm.com \
--cc=wg@denx.de \
/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).