From: Marc Zyngier <maz@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: "Liang, Kan" <kan.liang@linux.intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Conor Dooley <conor+dt@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Ian Rogers <irogers@google.com>, Ingo Molnar <mingo@redhat.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
John Garry <john.g.garry@oracle.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Leo Yan <leo.yan@linux.dev>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mike Leach <mike.leach@linaro.org>,
Namhyung Kim <namhyung@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Peter Zijlstra <peterz@infradead.org>,
Rob Herring <robh@kernel.org>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
Will Deacon <will@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v3 5/6] arm64: dts: renesas: Add R8A78000 X5H DTs
Date: Tue, 16 Sep 2025 11:45:15 +0100 [thread overview]
Message-ID: <86v7li1xs4.wl-maz@kernel.org> (raw)
In-Reply-To: <87ms6vi0js.wl-kuninori.morimoto.gx@renesas.com>
On Tue, 16 Sep 2025 03:38:47 +0100,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> wrote:
>
> From: Hai Pham <hai.pham.ud@renesas.com>
>
> Add initial DT support for R8A78000 (R-Car X5H) SoC.
>
> [Kuninori: tidyup for upstreaming]
>
> Signed-off-by: Hai Pham <hai.pham.ud@renesas.com>
> Signed-off-by: Vinh Nguyen <vinh.nguyen.xz@renesas.com>
> Signed-off-by: Minh Le <minh.le.aj@renesas.com>
> Signed-off-by: Huy Bui <huy.bui.wm@renesas.com>
> Signed-off-by: Khanh Le <khanh.le.xr@renesas.com>
> Signed-off-by: Phong Hoang <phong.hoang.wz@renesas.com>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
> arch/arm64/boot/dts/renesas/r8a78000.dtsi | 756 ++++++++++++++++++++++
> 1 file changed, 756 insertions(+)
> create mode 100644 arch/arm64/boot/dts/renesas/r8a78000.dtsi
>
> diff --git a/arch/arm64/boot/dts/renesas/r8a78000.dtsi b/arch/arm64/boot/dts/renesas/r8a78000.dtsi
> new file mode 100644
> index 0000000000000..82e27ce39c127
> --- /dev/null
> +++ b/arch/arm64/boot/dts/renesas/r8a78000.dtsi
[...]
> + soc: soc {
> + compatible = "simple-bus";
> + interrupt-parent = <&gic>;
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + prr: chipid@189e0044 {
> + compatible = "renesas,prr";
> + reg = <0 0x189e0044 0 4>;
> + };
> +
> + /*
> + * The ARM GIC-720AE - View 1
> + *
> + * see
> + * r19uh0244ej0052-r-carx5h.pdf
> + * - attachments: 002_R-CarX5H_Address_Map_r0p51.xlsx
> + * - sheet [RT]
> + * - line 619
Are these documents publicly available? If not, I don't think this
helps much.
> + */
> + gic: interrupt-controller@39000000 {
> + compatible = "arm,gic-v3";
> + #interrupt-cells = <3>;
> + #address-cells = <0>;
> + interrupt-controller;
> + reg = <0 0x39000000 0 0x20000>, // GICD
> + <0 0x39080000 0 0x40000>; // GICR
In v2, you indicated that your GIC was configured for GICv4.1, which
implied 256kB frames for each redistributor. Here, you have either
just enough space for 32 RDs for a GICv3, or 16 RDs for GICv4.
So either this is wrong, and you're missing half of the RD space, or
v2 was wrong. Which one is it?
> + interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>;
No ITS? That seems... surprising.
> + };
[...]
> + timer {
> + compatible = "arm,armv8-timer";
> + interrupts-extended = <&gic GIC_PPI 13 IRQ_TYPE_LEVEL_LOW>,
> + <&gic GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>,
> + <&gic GIC_PPI 11 IRQ_TYPE_LEVEL_LOW>,
> + <&gic GIC_PPI 10 IRQ_TYPE_LEVEL_LOW>,
> + <&gic GIC_PPI 12 IRQ_TYPE_LEVEL_LOW>;
> + interrupt-names = "sec-phys", "phys", "virt", "hyp-phys",
> + "hyp-virt";
> + };
Why use interrupts-extended here? Everywhere else, you're using the
basic interrupt specifier. Can't you move the interrupt-parent
property to the top and simplify the timer (and everything else
outside of the 'soc' node?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-09-16 10:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 2:37 [PATCH v3 0/6] arm64: add R8A78000 support Kuninori Morimoto
2025-09-16 2:38 ` [PATCH v3 1/6] dt-bindings: soc: renesas: Document R-Car X5H Ironhide Kuninori Morimoto
2025-09-16 10:18 ` Geert Uytterhoeven
2025-09-16 2:38 ` [PATCH v3 2/6] soc: renesas: Identify R-Car X5H Kuninori Morimoto
2025-09-16 10:19 ` Geert Uytterhoeven
2025-09-16 2:38 ` [PATCH v3 3/6] arm64: cputype: Add Cortex-A720AE definitions Kuninori Morimoto
2025-09-16 8:53 ` Will Deacon
2025-09-16 11:10 ` Mark Rutland
2025-09-16 2:38 ` [PATCH v3 4/6] dt-bindings: arm: cpus: Add Cortex-A720AE Kuninori Morimoto
2025-09-16 10:21 ` Geert Uytterhoeven
2025-09-16 2:38 ` [PATCH v3 5/6] arm64: dts: renesas: Add R8A78000 X5H DTs Kuninori Morimoto
2025-09-16 10:45 ` Marc Zyngier [this message]
2025-09-17 4:08 ` Kuninori Morimoto
2025-09-17 7:53 ` Marc Zyngier
2025-09-17 17:52 ` Wolfram Sang
2025-09-18 0:19 ` Kuninori Morimoto
2025-09-16 2:38 ` [PATCH v3 6/6] arm64: dts: renesas: R8A78000: Add initial Ironhide support Kuninori Morimoto
2025-09-17 15:00 ` [PATCH v3 0/6] arm64: add R8A78000 support Rob Herring (Arm)
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=86v7li1xs4.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=geert+renesas@glider.be \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=krzk+dt@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=will@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).