From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] arm64: dts: zx: Fix gic GICR property
Date: Sat, 3 Dec 2016 17:22:55 +0800 [thread overview]
Message-ID: <20161203092251.GA17375@dragon> (raw)
In-Reply-To: <a243d381-f7ab-abed-ca21-f0951abb04fd@arm.com>
On Fri, Dec 02, 2016 at 05:02:28PM +0000, Marc Zyngier wrote:
> Just noticed this.
>
> On 13/10/16 13:31, Jun Nie wrote:
> > GICR for multiple CPU can be described with start address and stride,
> > or with multiple address. Current multiple address and stride are
> > both used. Fix it.
> >
> > vmalloc patch 727a7f5a9 triggered this bug:
> > [ 0.097146] Unable to handle kernel paging request at virtual address ffff000008060008
> > [ 0.097150] pgd = ffff000008602000
> > [ 0.097160] [ffff000008060008] *pgd=000000007fffe003, *pud=000000007fffd003, *pmd=000000007fffc003, *pte=0000000000000000
> > [ 0.097165] Internal error: Oops: 96000007 [#1] PREEMPT SMP
> > [ 0.097170] Modules linked in:
> > [ 0.097177] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.8.0+ #1474
> > [ 0.097179] Hardware name: ZTE zx296718 evaluation board (DT)
> > [ 0.097183] task: ffff80003e8c8b80 task.stack: ffff80003e8d0000
> > [ 0.097197] PC is at gic_populate_rdist+0x74/0x15c
> > [ 0.097202] LR is at gic_starting_cpu+0xc/0x20
> > [ 0.097206] pc : [<ffff0000082b1b18>] lr : [<ffff0000082b26e0>] pstate: 600001c5
> >
> > Signed-off-by: Jun Nie <jun.nie@linaro.org>
> > ---
> > arch/arm64/boot/dts/zte/zx296718.dtsi | 11 +++--------
> > 1 file changed, 3 insertions(+), 8 deletions(-)
> >
> > diff --git a/arch/arm64/boot/dts/zte/zx296718.dtsi b/arch/arm64/boot/dts/zte/zx296718.dtsi
> > index a223066..6b239a3 100644
> > --- a/arch/arm64/boot/dts/zte/zx296718.dtsi
> > +++ b/arch/arm64/boot/dts/zte/zx296718.dtsi
> > @@ -239,16 +239,11 @@
> > compatible = "arm,gic-v3";
> > #interrupt-cells = <3>;
> > #address-cells = <0>;
> > - #redistributor-regions = <6>;
> > - redistributor-stride = <0x0 0x40000>;
> > + #redistributor-regions = <1>;
> > + redistributor-stride = <0x20000>;
>
> Why is that stride specified? Is the GIC implementation so busted that
> the GICR_TYPER do not report a GICv3 redistributor, which implies a
> 128kB stride?
No, it's not required per my testing. I guess it's there for
documentation purpose to make the stride setting explicit. Are you
suggesting that we simply drop it?
Also, it seems that #redistributor-regions can also be saved, since
bindings doc tells that it's only required if more than one such region
is present?
Shawn
next prev parent reply other threads:[~2016-12-03 9:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 12:31 [PATCH v2 0/2] Fix and add more zx dt nodes Jun Nie
2016-10-13 12:31 ` [PATCH v2 1/2] arm64: dts: zx: Fix gic GICR property Jun Nie
2016-10-17 20:49 ` Olof Johansson
2016-11-25 22:03 ` Arnd Bergmann
2016-11-28 14:08 ` Shawn Guo
2016-12-02 16:38 ` Arnd Bergmann
2016-12-03 10:55 ` Shawn Guo
2016-12-02 17:02 ` Marc Zyngier
2016-12-02 20:28 ` Arnd Bergmann
2016-12-05 2:24 ` Shawn Guo
2016-12-06 0:55 ` Olof Johansson
2016-12-06 1:12 ` Shawn Guo
2016-12-07 20:34 ` Olof Johansson
2016-12-07 21:44 ` Arnd Bergmann
2016-12-07 22:12 ` Olof Johansson
2016-12-07 23:25 ` Arnd Bergmann
2016-12-03 9:22 ` Shawn Guo [this message]
2016-12-03 10:11 ` Marc Zyngier
2016-10-13 12:31 ` [PATCH v2 2/2] arm64: dts: zx: Add clock controller nodes Jun Nie
2016-10-17 20:48 ` Olof Johansson
2016-10-24 8:56 ` Shawn Guo
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=20161203092251.GA17375@dragon \
--to=shawnguo@kernel.org \
--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).