From: sashiko-bot@kernel.org
To: "Gregor Herburger" <gregor.herburger@linutronix.de>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: broadcom: bcm2712-rpi-5-b: add spi0 interface
Date: Fri, 04 Sep 2026 09:32:59 +0000 [thread overview]
Message-ID: <20260904093259.D19D31F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260904-bcm2712-spi-v2-1-6f8fdfb030bc@linutronix.de>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Device tree compilation fails due to an undefined phandle reference to `rp1_spi0`.
--
commit 330478d6863965c56268ce6533d5e3b957169da2
Author: Gregor Herburger <gregor.herburger@linutronix.de>
arm64: dts: broadcom: bcm2712-rpi-5-b: add spi0 interface
This commit adds the rp1_spi0 node and its pinctrl node to the bcm2712-rpi-5-b
devicetree to route spi0 to the pin header.
Link to v1: https://patch.msgid.link/20260811-bcm2712-spi-v1-0-4c1708d354bb@linutronix.de
> diff --git a/arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dts b/arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dts
> index 0fc57e72632ed..0de3d78100a5d 100644
> --- a/arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dts
> +++ b/arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dts
[ ... ]
> @@ -94,6 +108,14 @@ &rp1_i2c6 {
> pinctrl-names = "default";
> };
>
> +&rp1_spi0 {
[Severity: Low]
Will this cause the device tree compiler (dtc) to fail with a "Reference to
non-existent node or label" error?
It looks like the rp1_spi0 label is undefined in this revision. The patch
notes mention dropping the first patch because it was already applied, but it
seems the prerequisite patch providing the rp1_spi0 base node is missing from
the tree at this revision.
> + pinctrl-0 = <&rp1_spi0_default_state &rp1_spi0_cs_default_state>;
> + pinctrl-names = "default";
> +
> + num-cs = <2>;
> + cs-gpios = <&rp1_gpio 8 GPIO_ACTIVE_LOW &rp1_gpio 7 GPIO_ACTIVE_LOW>;
> +};
> +
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260904-bcm2712-spi-v2-1-6f8fdfb030bc@linutronix.de?part=1
next prev parent reply other threads:[~2026-09-04 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 9:24 [PATCH v2] arm64: dts: broadcom: bcm2712-rpi-5-b: add spi0 interface Gregor Herburger
2026-09-04 9:32 ` sashiko-bot [this message]
2026-09-04 10:33 ` Andrea della Porta
2026-09-04 10:54 ` Gregor Herburger
2026-09-04 22:31 ` Florian Fainelli
2026-09-04 22:27 ` Florian Fainelli
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=20260904093259.D19D31F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregor.herburger@linutronix.de \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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