From: Rob Herring <robherring2@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Peter De Schrijver <pdeschrijver@nvidia.com>,
Marc Dietrich <marvin24@gmx.de>, Olof Johansson <olof@lixom.net>,
Russell King <linux@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Colin Cross <ccross@android.com>
Subject: Re: [PATCH] arm/tegra: convert tegra20 to GIC devicetree binding
Date: Thu, 17 Nov 2011 11:15:30 -0600 [thread overview]
Message-ID: <4EC54132.5070908@gmail.com> (raw)
In-Reply-To: <CACxGe6ub2QBO0ZLwNdSvMxP1U087pqL-qL+dfWAbn-08gBQyvg@mail.gmail.com>
On 11/17/2011 10:53 AM, Grant Likely wrote:
>
> On Nov 17, 2011 8:54 AM, "Peter De Schrijver" <pdeschrijver@nvidia.com
> <mailto:pdeschrijver@nvidia.com>> wrote:
>>
>> On Thu, Nov 17, 2011 at 04:44:15PM +0100, Rob Herring wrote:
>> > On 11/17/2011 09:07 AM, Peter De Schrijver wrote:
>> > > Convert tegra20 IRQ intialization to the GIC devicetree binding.
> Modify the
>> > > interrupt definitions in the dts files according to
>> > > Documentation/devicetree/bindings/arm/gic.txt
>> > >
>> > > Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com
> <mailto:pdeschrijver@nvidia.com>>
>> >
>> > One minor comment below, but otherwise:
>> >
>> > Acked-by: Rob Herring <rob.herring@calxeda.com
> <mailto:rob.herring@calxeda.com>>
>> >
>> > > ---
>> > > arch/arm/boot/dts/tegra-paz00.dts | 2 +-
>> > > arch/arm/boot/dts/tegra20.dtsi | 52
> ++++++++++++++++++------------------
>> > > arch/arm/mach-tegra/irq.c | 18 +++++++++++-
>> > > 3 files changed, 43 insertions(+), 29 deletions(-)
>> > >
>> > > diff --git a/arch/arm/boot/dts/tegra-paz00.dts
> b/arch/arm/boot/dts/tegra-paz00.dts
>> > > index 15a949f..7ff8f6f 100644
>> > > --- a/arch/arm/boot/dts/tegra-paz00.dts
>> > > +++ b/arch/arm/boot/dts/tegra-paz00.dts
>> > > @@ -32,7 +32,7 @@
>> > > #size-cells = <0>;
>> > > compatible = "nvidia,nvec";
>> > > reg = <0x7000C500 0x100>;
>> > > - interrupts = <124>;
>> > > + interrupts = <0 92 0x04>;
>> > > clock-frequency = <80000>;
>> > > request-gpios = <&gpio 170 0>;
>> > > slave-addr = <138>;
>> > > diff --git a/arch/arm/boot/dts/tegra20.dtsi
> b/arch/arm/boot/dts/tegra20.dtsi
>> > > index 795b921..cd01b01 100644
>> > > --- a/arch/arm/boot/dts/tegra20.dtsi
>> > > +++ b/arch/arm/boot/dts/tegra20.dtsi
>> > > @@ -5,9 +5,9 @@
>> > > interrupt-parent = <&intc>;
>> > >
>> > > intc: interrupt-controller@50041000 {
>> > > - compatible = "nvidia,tegra20-gic";
>> > > + compatible = "arm,cortex-a9-gic";
>> > > interrupt-controller;
>> >
>> > You should add an "interrupt-parent;" here so the gic's parent is null
>> > and not the gic.
>>
>> Ok. I will add that in the next version.
>
> No, there is no need to do that, nor is it convention. The gic node
> doesn't have an interrupts property, so the interrupt-parent is irrelevant.
>
Can't resist the inbox? Go back to your sabbatical.. :) We discussed
this before and I though agreed this was the correct approach.
It inherits the interrupt-parent from the parent node. Originally
of_irq_find_parent would return that node, but this was fixed. So it
doesn't really matter from a functional standpoint.
So is no interrupt parent defined as no interrupts property or
interrupt-parent being null phandle?
> Rob, perhaps we should adjust of_init_irq() to only set the parent
> pointer if interrupts is present.
>
It works correctly already either way.
Rob
next prev parent reply other threads:[~2011-11-17 17:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 15:07 [PATCH] arm/tegra: convert tegra20 to GIC devicetree binding Peter De Schrijver
[not found] ` <1321542430-17971-1-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-11-17 15:44 ` Rob Herring
[not found] ` <4EC52BCF.7020609-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-11-17 15:54 ` Peter De Schrijver
[not found] ` <CACxGe6ub2QBO0ZLwNdSvMxP1U087pqL-qL+dfWAbn-08gBQyvg@mail.gmail.com>
2011-11-17 17:15 ` Rob Herring [this message]
[not found] ` <4EC54132.5070908-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-11-17 20:41 ` Grant Likely
2011-11-17 18:51 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF1740D74C1E-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-11-18 12:03 ` Peter De Schrijver
2011-11-18 12:03 ` Peter De Schrijver
[not found] ` <20111118120352.GZ19069-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2011-11-18 16:25 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF1740D74E63-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-11-21 12:22 ` Peter De Schrijver
[not found] ` <20111121122212.GL19069-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2011-11-21 17:20 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF174F08C0E5-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-11-23 5:00 ` Peter De Schrijver
[not found] ` <20111123050012.GS19069-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2011-11-23 17:25 ` Stephen Warren
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=4EC54132.5070908@gmail.com \
--to=robherring2@gmail.com \
--cc=ccross@android.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marvin24@gmx.de \
--cc=olof@lixom.net \
--cc=pdeschrijver@nvidia.com \
--cc=swarren@nvidia.com \
/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