[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdVanMOXFNEAne+HhE-5eHa43kxRvexWHpGjXDdHnJp2bQ@mail.gmail.com>
Date: Thu, 27 Nov 2025 17:40:14 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Prabhakar <prabhakar.csengg@...il.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Magnus Damm <magnus.damm@...il.com>, Fabrizio Castro <fabrizio.castro.jz@...esas.com>,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-renesas-soc@...r.kernel.org, Biju Das <biju.das.jz@...renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
Subject: Re: [PATCH v2 2/2] irqchip: renesas: rzv2h-icu: Add support for
RZ/V2N SoC
On Thu, 27 Nov 2025 at 17:24, Prabhakar <prabhakar.csengg@...il.com> wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
>
> Add support for the RZ/V2N Interrupt Control Unit (ICU) by introducing a
> dedicated compatible string in the irqchip driver. While the RZ/V2N ICU
> differs from the RZ/V2H(P) version in its register layout primarily due
> to a reduced set of ECCRAM related registers the irqchip driver does not
> currently access these registers.
>
> As a result, the RZ/V2N ICU can be safely handled by rzv2h_icu_probe for
> now, but it still requires a distinct compatible so that future changes
> can differentiate the SoCs when needed.
>
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@...der.be>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists