From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Dirk Behme <dirk.behme@de.bosch.com>,
linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Marc Zyngier <Marc.Zyngier@arm.com>
Subject: Re: [PATCH v2] arm64: dts: r8a7795: Add GIC-400 virtual interfaces
Date: Wed, 17 Feb 2016 15:33:17 +0900 [thread overview]
Message-ID: <20160217063316.GL11534@verge.net.au> (raw)
In-Reply-To: <CAMuHMdVP4wA4eXK-fkENndNs=zS2vuUeDww2ZZbXvocfFiOgWQ@mail.gmail.com>
On Tue, Feb 16, 2016 at 10:55:37AM +0100, Geert Uytterhoeven wrote:
> CC Marc
>
> On Tue, Feb 16, 2016 at 10:43 AM, Dirk Behme <dirk.behme@de.bosch.com> wrote:
> > Besides the distributor and the CPU interface the GIC-400 additionally
> > supports the virtual interface control blocks and the virtual CPU interfaces.
> >
> > Add the physical base addresses and size for these.
> >
> > See
> >
> > http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0471b/index.html
> > -> 3.2. GIC-400 register map
> >
> > and Linux kernel's
> >
> > Documentation/devicetree/bindings/interrupt-controller/arm,gic.txt
> >
> > for more details.
> >
> > For the at GICH Virtual interface control blocks at 0xf1040000 cover the
> > whole 128kB (0x20000) range. This is done based on the advice from Marc
> > Zyngier http://www.spinics.net/lists/arm-kernel/msg483139.html
> >
> > Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
>
> Thanks!
>
> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
Thanks, I have queued this up for v4.6.
prev parent reply other threads:[~2016-02-17 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 9:43 [PATCH v2] arm64: dts: r8a7795: Add GIC-400 virtual interfaces Dirk Behme
2016-02-16 9:55 ` Geert Uytterhoeven
2016-02-17 6:33 ` Simon Horman [this message]
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=20160217063316.GL11534@verge.net.au \
--to=horms@verge.net.au \
--cc=Marc.Zyngier@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dirk.behme@de.bosch.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.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).