From: Marc Zyngier <marc.zyngier@arm.com>
To: Mark Rutland <mark.rutland@arm.com>,
Soren Brinkmann <soren.brinkmann@xilinx.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Michal Simek <michal.simek@xilinx.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Alistair Francis <alistair.francis@xilinx.com>
Subject: Re: [PATCH] ARM64: ZynqMP: DT: Fix GIC's 'reg' property
Date: Mon, 14 Dec 2015 17:01:00 +0000 [thread overview]
Message-ID: <566EF5CC.4070000@arm.com> (raw)
In-Reply-To: <20151214164613.GH21356@leverpostej>
Mark,
On 14/12/15 16:46, Mark Rutland wrote:
> On Mon, Dec 14, 2015 at 08:31:40AM -0800, Soren Brinkmann wrote:
>> Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com>
>> ---
>> arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
>> index 857eda5c7217..b5d1facadf16 100644
>> --- a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
>> +++ b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
>> @@ -80,10 +80,10 @@
>> gic: interrupt-controller@f9010000 {
>> compatible = "arm,gic-400", "arm,cortex-a15-gic";
>> #interrupt-cells = <3>;
>> - reg = <0x0 0xf9010000 0x10000>,
>> - <0x0 0xf902f000 0x2000>,
>> + reg = <0x0 0xf9010000 0x1000>,
>> + <0x0 0xf9020000 0x20000>,
>> <0x0 0xf9040000 0x20000>,
>> - <0x0 0xf906f000 0x2000>;
>> + <0x0 0xf9060000 0x20000>;
>
> I'm confused. These sizes don't look right for GIC-400. Is this a custom
> GIC?
Probably an implementation that obey the SBSA requirement of aliasing
the first 4kB of the CPU interface on a 64kB page, and the second one on
the following 64kB page. See the APM system for an example of such a
thing. I'm more concerned about the GICH region (3rd one), which has no
reason to be bigger than 4kB.
> Did this ever work wit hteh old offsets and sizes?
It probably dies when trying to use EOImode==1.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-12-14 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 16:31 [PATCH] ARM64: ZynqMP: DT: Fix GIC's 'reg' property Soren Brinkmann
[not found] ` <1450110700-14152-1-git-send-email-soren.brinkmann-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2015-12-14 16:46 ` Mark Rutland
2015-12-14 17:01 ` Marc Zyngier [this message]
[not found] ` <566EF5CC.4070000-5wv7dgnIgG8@public.gmane.org>
2015-12-15 9:14 ` Sören Brinkmann
2015-12-15 15:01 ` Michal Simek
[not found] ` <56702B44.5080201-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2015-12-16 9:01 ` Sören Brinkmann
2015-12-16 9:07 ` Marc Zyngier
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=566EF5CC.4070000@arm.com \
--to=marc.zyngier@arm.com \
--cc=alistair.francis@xilinx.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=soren.brinkmann@xilinx.com \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).