linux-kernel - Re: [PATCH 5.15 110/317] arm64: dts: renesas: r8a779a0: Update to R-Car Gen4 compatible values

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Tue, 2 Apr 2024 10:57:41 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org, 
	Wolfram Sang <wsa+renesas@...g-engineering.com>
Subject: Re: [PATCH 5.15 110/317] arm64: dts: renesas: r8a779a0: Update to
 R-Car Gen4 compatible values

Hi Sasha,

Looks like I missed some things in my previous review...

On Mon, Mar 25, 2024 at 12:36 AM Sasha Levin <sashal@...nel.org> wrote:
> From: Geert Uytterhoeven <geert+renesas@...der.be>
>
> [ Upstream commit a1721bbbdb5c6687d157f8b8714bba837f6028ac ]

This is not the corresponding upstream commit for this commit
(a022251c2f950cd2 in v5.15.153).
It should be a1ca409cc050166a9e8ed183c1d4192f511cf6a2.
How could that happen? Interestingly, the backport in v6.1.83
(efab55e16c55c637) does have the correct upstream commit.

> Despite the name, R-Car V3U is the first member of the R-Car Gen4
> family.  Hence update the compatible properties in various device nodes
> to include family-specific compatible values for R-Car Gen4 instead of
> R-Car Gen3:
>   - DMAC,
>   - (H)SCIF,
>   - I2C,
>   - IPMMU,
>   - WDT.

Likewise, the description should be:

    Despite the name, R-Car V3U is the first member of the R-Car Gen4
    family.  Hence update the compatible properties in various device nodes
    to include family-specific compatible values for R-Car Gen4 instead of
    R-Car Gen3:
      - EtherAVB,
      - MSIOF.

> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
> Reviewed-by: Wolfram Sang <wsa+renesas@...g-engineering.com>

Likewise, bogus tag never given...

> Link: https://lore.kernel.org/r/73cea9d5e1a6639422c67e4df4285042e31c9fd5.1651497071.git.geert+renesas@glider.be

and a wrong link.

> Stable-dep-of: 0c51912331f8 ("arm64: dts: renesas: r8a779a0: Correct avb[01] reg sizes")
> Signed-off-by: Sasha Levin <sashal@...nel.org>

> --- a/arch/arm64/boot/dts/renesas/r8a779a0.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a779a0.dtsi

> @@ -935,7 +935,7 @@ scif4: serial@...40000 {
>
>                 msiof0: spi@...90000 {
>                         compatible = "renesas,msiof-r8a779a0",
> -                                    "renesas,rcar-gen3-msiof";
> +                                    "renesas,rcar-gen4-msiof";

The Renesas MSIOF driver in v5.15.153 does not handle
"renesas,rcar-gen4-msiof" yet.  Please backport commit ea9d001550abaf2f
("spi: sh-msiof: add generic Gen4 binding") in v6.1 to fix that.

>                         reg = <0 0xe6e90000 0 0x0064>;
>                         interrupts = <GIC_SPI 245 IRQ_TYPE_LEVEL_HIGH>;
>                         clocks = <&cpg CPG_MOD 618>;

Thanks!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68korg

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