All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 3/4] arm64: dts: renesas: Add R8A78000 X5H DTs
Date: Fri, 12 Sep 2025 11:25:13 +0100	[thread overview]
Message-ID: <868qikc6ie.wl-maz@kernel.org> (raw)
In-Reply-To: <CAMuHMdX3cviP6xHnGP01kRDwuHRrHg0ZpNLV8Mf29MFS1B7S8g@mail.gmail.com>

On Fri, 12 Sep 2025 08:37:29 +0100,
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> 
> Hi Morimoto-san,
> 
> CC maz
> 
> On Fri, 12 Sept 2025 at 02:39, Kuninori Morimoto
> <kuninori.morimoto.gx@renesas.com> wrote:
> > > > +               /* The Arm GIC-700AE - View 1 */
> > >
> > > s/700/720/
> >
> > Oops, thanks. Will fix
> >
> > > > +               gic: interrupt-controller@39000000 {
> > > > +                       compatible = "arm,gic-v3";
> > >
> > > The documentation states it is compliant with GICv4.1?
> >
> > I'm not familiar with GIC. And I think there is no v4 support on Linux yet ?
> > If my understanding was correct, GICv4 have GICv3 compatible.
> > We can use v3 driver so far, and can be replaced to v4 driver if it was
> > supported in Linux?
> 
> 'git grep -i "\<gic.*v4.1"' does show support.
> 
> Marc?

We don't need to differentiate the various GICv3.{0,1,2,3} and
GICv4.{0,1,2} in DT. GICv3 is enough, and everything is else can be
probed.

And yes, we support everything (but that's not relevant for DT).

> 
> > > > +                       #interrupt-cells = <3>;
> > > > +                       #address-cells = <0>;
> > > > +                       interrupt-controller;
> > > > +                       redistributor-stride = <0x0 0x40000>;

No. That's the architected value, and doesn't need to be described.
This property is solely designed to support broken HW, and I really
hope this is not the case here.

> > > > +                       #redistributor-regions = <32>;
> > > > +                       reg = <0 0x39000000 0 0x20000>, // GICD
> > >
> > > The base address is 0x38000000, according to the docs?
> >
> > It is indicated in very deep place in datasheet. I will indicate
> > detail in v2.
> >
> > > > +                             <0 0x397C0000 0 0x40000>, // GICR Core29
> > > > +                             <0 0x39800000 0 0x40000>, // GICR Core30
> > > > +                             <0 0x39840000 0 0x40000>; // GICR Core31

This really is silly. You have *one* RD region, not 32. This single
region covers all the RDs that your system has.

> > >
> > > No GICC, GICH, and GICV?
> >
> > will be added later ?
> 
> OK.

I seriously doubt you can have these regions, unless you have attached
a GIC700 to an ancient core such as A53. Here, you seem to have a
bunch of A720, which will *not* have the GICv2 compat regions.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2025-09-12 10:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10  2:01 [PATCH v2 0/4] arm64: add R8A78000 support Kuninori Morimoto
2025-09-10  2:01 ` [PATCH v2 1/4] dt-bindings: soc: renesas: Document R-Car X5H Ironhide Kuninori Morimoto
2025-09-10 12:27   ` Geert Uytterhoeven
2025-09-10  2:01 ` [PATCH v2 2/4] soc: renesas: Identify R-Car X5H Kuninori Morimoto
2025-09-10 12:28   ` Geert Uytterhoeven
2025-09-10  2:01 ` [PATCH v2 3/4] arm64: dts: renesas: Add R8A78000 X5H DTs Kuninori Morimoto
2025-09-10 14:18   ` Geert Uytterhoeven
2025-09-12  0:39     ` Kuninori Morimoto
2025-09-12  7:37       ` Geert Uytterhoeven
2025-09-12 10:25         ` Marc Zyngier [this message]
2025-09-16  0:52         ` Kuninori Morimoto
2025-09-16  7:51           ` Geert Uytterhoeven
2025-09-18  5:13             ` Kuninori Morimoto
2025-09-10  2:01 ` [PATCH v2 4/4] arm64: renesas: Add R8A78000 Ironhide board code Kuninori Morimoto
2025-09-10 14:19   ` Geert Uytterhoeven

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=868qikc6ie.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=krzk+dt@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.