linux-kernel - Re: linux-next: build warnings after merge of the renesas tree

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] [day] [month] [year] [list]

Message-ID: <CAMuHMdX_K7EA4kE2mqxv+BkfR_oQmcpek2B3LxiYxMjSMfwjAw@mail.gmail.com>
Date: Tue, 6 May 2025 12:05:15 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	Linux Next Mailing List <linux-next@...r.kernel.org>, 
	Devicetree Compiler <devicetree-compiler@...r.kernel.org>, 
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree@...r.kernel.org>
Subject: Re: linux-next: build warnings after merge of the renesas tree

Hi Stephen,

On Tue, 6 May 2025 at 11:20, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> After merging the renesas tree, today's linux-next build (arm64 defconfig)
> produced these warnings:
>
> arch/arm64/boot/dts/renesas/r8a779g0.dtsi:1269.24-1283.5: Warning (spi_bus_bridge): /soc/spi@...a0000: incorrect #address-cells for SPI bus
>   also defined at arch/arm64/boot/dts/renesas/r8a779g3-sparrow-hawk.dts:463.9-478.3
> arch/arm64/boot/dts/renesas/r8a779g0.dtsi:1269.24-1283.5: Warning (spi_bus_bridge): /soc/spi@...a0000: incorrect #size-cells for SPI bus
>   also defined at arch/arm64/boot/dts/renesas/r8a779g3-sparrow-hawk.dts:463.9-478.3
> arch/arm64/boot/dts/renesas/r8a779g3-sparrow-hawk.dtb: Warning (spi_bus_reg): Failed prerequisite 'spi_bus_bridge'
>
> Introduced by commit
>
>   c29748ccad88 ("arm64: dts: renesas: sparrow-hawk: Add MSIOF Sound support")

Thanks, this is a known conflict between SPI bus bindings and dtc:
  - Serial engines that can be SPI controllers must use "spi" as their
    node names,
  - Dtc assumes nodes named "spi" are always SPI controllers.

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