From: Kevin Hilman <khilman@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: "Chalamarla\,
Tirumalesh" <Tirumalesh.Chalamarla@caviumnetworks.com>,
"marc.zyngier\@arm.com" <marc.zyngier@arm.com>,
"Will.Deacon\@arm.com" <Will.Deacon@arm.com>,
"rrichter\@cavium.com" <rrichter@cavium.com>,
"devicetree\@vger.kernel.org" <devicetree@vger.kernel.org>,
Tirumalesh Chalamarla <tchalamarla@cavium.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
arm@kernel.org
Subject: Re: [PATCH] GICv3: Add ITS entry to THUNDER dts
Date: Wed, 08 Jul 2015 14:26:33 -0700 [thread overview]
Message-ID: <7hpp42cpdi.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20150703095755.GH25907@e104818-lin.cambridge.arm.com> (Catalin Marinas's message of "Fri, 3 Jul 2015 10:57:56 +0100")
Catalin Marinas <catalin.marinas@arm.com> writes:
> On Thu, Jul 02, 2015 at 08:26:02PM +0000, Chalamarla, Tirumalesh wrote:
>> > On Jun 26, 2015, at 12:12 PM, Tirumalesh Chalamarla <tchalamarla@caviumnetworks.com> wrote:
>> >
>> > From: Tirumalesh Chalamarla <tchalamarla@cavium.com>
>> >
>> > The PCIe host controller uses MSIs provided by GICv3 ITS. Enable it on
>> > Thunder SoCs by adding an entry to DT.
>> >
>> > Signed-off-by: Tirumalesh Chalamarla <tchalamarla@cavium.com>
>> > Acked-by: Marc Zyngier <marc.zyngier@arm.com>
>> > ---
>> > arch/arm64/boot/dts/cavium/thunder-88xx.dtsi | 9 +++++++++
>> > 1 file changed, 9 insertions(+)
>> >
>> > diff --git a/arch/arm64/boot/dts/cavium/thunder-88xx.dtsi b/arch/arm64/boot/dts/cavium/thunder-88xx.dtsi
>> > index d8c0bdc..9cb7cf9 100644
>> > --- a/arch/arm64/boot/dts/cavium/thunder-88xx.dtsi
>> > +++ b/arch/arm64/boot/dts/cavium/thunder-88xx.dtsi
>> > @@ -376,10 +376,19 @@
>> > gic0: interrupt-controller@8010,00000000 {
>> > compatible = "arm,gic-v3";
>> > #interrupt-cells = <3>;
>> > + #address-cells = <2>;
>> > + #size-cells = <2>;
>> > + ranges;
>> > interrupt-controller;
>> > reg = <0x8010 0x00000000 0x0 0x010000>, /* GICD */
>> > <0x8010 0x80000000 0x0 0x600000>; /* GICR */
>> > interrupts = <1 9 0xf04>;
>> > +
>> > + its: gic-its@8010,00020000 {
>> > + compatible = "arm,gic-v3-its";
>> > + msi-controller;
>> > + reg = <0x8010 0x20000 0x0 0x200000>;
>> > + };
>> > };
>> >
>> > uaa0: serial@87e0,24000000 {
>>
>> is it possible to pull this for 4.2?
>
> The dts files go in via the arm-soc tree (cc'ing arm@kernel.org).
Picked this up for v4.2-rc,
Kevin
next prev parent reply other threads:[~2015-07-08 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 19:12 [PATCH] GICv3: Add ITS entry to THUNDER dts Tirumalesh Chalamarla
2015-07-02 20:26 ` Chalamarla, Tirumalesh
2015-07-03 9:57 ` Catalin Marinas
2015-07-08 21:26 ` Kevin Hilman [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-26 19:10 Tirumalesh Chalamarla
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=7hpp42cpdi.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=Tirumalesh.Chalamarla@caviumnetworks.com \
--cc=Will.Deacon@arm.com \
--cc=arm@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=rrichter@cavium.com \
--cc=tchalamarla@cavium.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