From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] ARM: mach-shmobile: r8a7779: Allow initialisation of GIC by DT
Date: Mon, 4 Feb 2013 17:37:01 +0000 [thread overview]
Message-ID: <20130204173701.GE28464@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <510BCE09.7050302@gmail.com>
On Fri, Feb 01, 2013 at 02:15:37PM +0000, Rob Herring wrote:
> On 02/01/2013 04:58 AM, Mark Rutland wrote:
> > On Fri, Feb 01, 2013 at 12:34:10AM +0000, Simon Horman wrote:
> >> On Fri, Feb 01, 2013 at 09:11:19AM +0900, Simon Horman wrote:
> >>> On Thu, Jan 31, 2013 at 12:32:13PM +0000, Mark Rutland wrote:
> >>>> Hi Simon,
> >>>>
> >>>> On Thu, Jan 31, 2013 at 01:50:49AM +0000, Simon Horman wrote:
>
> >>>>> +
> >>>>> + gic: interrupt-controller at f0001000 {
> >>>>> + compatible = "arm,cortex-a9-gic";
> >>>>> + #interrupt-cells = <3>;
> >>>>> + #address-cells = <1>;
> >>>>
> >>>> Why is #address-cells needed here (and without #size-cells)? I see it's in the
> >>>> binding document example, but I can't figure out why.
> >>>
> >>> Its here because I copied the example.
> >>> I will see about removing it from here.
> >
> > Rob, Grant, do either of you know if there's a reason for this that we've
> > missed?
> >
> > The gic doesn't have any direct children, and this doesn't seem to be
> > some decvicetree interrupt-controller magic.
>
> If you look at of_irq_map_raw, there are cases that look at
> #address-cells. Those appear to be only when you have an interrupt-map
> though.
Aah. So this is some devicetree magic after all. Thanks for looking into it.
> >
> > If this is superfluous, how about the patch below?
>
> The docs probably should state #addr-cells is only required with
> interrupt-map.
That'd be nice. It might limit the confusion we had here.
>
> >
> > I took a quick look at arch/arm/boot/dts/. Some gic nodes don't have
> > #address-cells, some have it but not #size-cells, and some have both. These
> > should probably be cleaned up too.
>
> Some boards are using interrupt-map, so they may need #address-cells. So
> I'm inclined to leave things alone.
That would make sense.
Thanks,
Mark.
next prev parent reply other threads:[~2013-02-04 17:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 1:50 ARM: mach-shmobile: r8a7779, marzen: Reference DT implementation Simon Horman
2013-01-31 1:50 ` [PATCH 1/4] ARM: mach-shmobile: marzen: defconfig: use regulators by default Simon Horman
2013-01-31 1:50 ` [PATCH 2/4] ARM: mach-shmobile: r8a7779: Allow initialisation of GIC by DT Simon Horman
2013-01-31 12:32 ` Mark Rutland
2013-02-01 0:11 ` Simon Horman
2013-02-01 0:34 ` Simon Horman
2013-02-01 1:47 ` Simon Horman
2013-02-01 4:39 ` Simon Horman
2013-02-01 11:31 ` Mark Rutland
2013-02-01 10:58 ` Mark Rutland
2013-02-01 14:15 ` Rob Herring
2013-02-04 17:37 ` Mark Rutland [this message]
2013-01-31 1:50 ` [PATCH 3/4] ARM: mach-shmobile: r8a7779: Minimal setup using DT Simon Horman
2013-02-18 9:36 ` Magnus Damm
2013-02-18 11:37 ` Simon Horman
2013-02-18 12:14 ` Magnus Damm
2013-02-18 12:37 ` Simon Horman
2013-02-18 12:22 ` Magnus Damm
2013-02-18 12:37 ` Simon Horman
2013-01-31 1:50 ` [PATCH 4/4] ARM: mach-shmobile: marzen: Reference DT implementation Simon Horman
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=20130204173701.GE28464@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--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).