From: sashiko-bot@kernel.org
To: "Aurelien Jarno" <aurelien@aurel32.net>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/5] riscv: dts: spacemit: k3: move USB3 phy to board level
Date: Mon, 31 Aug 2026 04:54:47 +0000 [thread overview]
Message-ID: <20260831045448.58B591F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260831044540.3304350-2-aurelien@aurel32.net>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Removing 'phys' and 'phy-names' from the base k3.dtsi breaks DT schema validation (dtbs_check) for disabled nodes and improperly delegates fixed SoC routing to board files.
--
commit e9dc7ad92d5f4a805cf362fdd51c6ae160da1934
Author: Aurelien Jarno <aurelien@aurel32.net>
riscv: dts: spacemit: k3: move USB3 phy to board level
This commit moves the USB3 phy definitions from the SoC dtsi to the board
level dts files for the SpacemiT K3 SoC. It aims to prevent PHY mode
configuration errors when the combo PHY lines are used for PCIe rather than
USB3.
[ ... ]
> diff --git a/arch/riscv/boot/dts/spacemit/k3.dtsi b/arch/riscv/boot/dts/spacemit/k3.dtsi
> index c3f2dce0969c0..6f8d55eae6f6b 100644
> --- a/arch/riscv/boot/dts/spacemit/k3.dtsi
> +++ b/arch/riscv/boot/dts/spacemit/k3.dtsi
> @@ -452,9 +452,6 @@ usb3d: usb@81a00000 {
> <&syscon_apmu RESET_APMU_USB3_D_VCC>,
> <&syscon_apmu RESET_APMU_USB3_D_PHY>;
> reset-names = "ahb", "vcc", "phy";
> - phys = <&usb3d_u2phy>,
> - <&combophy 4 PHY_TYPE_USB3>;
> - phy-names = "usb2-phy", "usb3-phy";
[Severity: Low]
Does removing phys and phy-names from the base k3.dtsi break DT schema
validation (dtbs_check) for disabled nodes?
To satisfy the schema's minItems: 1 requirement while supporting board-level
combo PHY configuration, should the dedicated internal SoC PHY (usb3d_u2phy)
have been retained in the base file?
The dtbs_check validation will fail for any board DT that includes k3.dtsi
but does not override the usb3d node to provide the phys and phy-names
properties (e.g., k3-com260-ifx.dts and k3-deepcomputing-fml13v05.dts).
This happens because the schema spacemit,k1-dwc3.yaml unconditionally
requires these properties, and dt-schema evaluates all nodes, even disabled
ones.
> phy_type = "utmi";
> snps,dis_enblslpm_quirk;
> snps,dis_u2_susphy_quirk;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260831044540.3304350-1-aurelien@aurel32.net?part=1
next prev parent reply other threads:[~2026-08-31 4:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 4:44 [PATCH v3 0/5] Enable Bluetooth and WiFi on K3 Pico ITX Aurelien Jarno
2026-08-31 4:44 ` Aurelien Jarno
2026-08-31 4:44 ` [PATCH v3 1/5] riscv: dts: spacemit: k3: move USB3 phy to board level Aurelien Jarno
2026-08-31 4:44 ` Aurelien Jarno
2026-08-31 4:54 ` sashiko-bot [this message]
2026-09-27 21:18 ` Aurelien Jarno
2026-09-27 21:18 ` Aurelien Jarno
2026-08-31 4:44 ` [PATCH v3 2/5] riscv: dts: spacemit: k3: add USB3 B and C controllers for Pico-ITX board Aurelien Jarno
2026-08-31 4:44 ` Aurelien Jarno
2026-08-31 4:44 ` [PATCH v3 3/5] riscv: dts: spacemit: k3: add rfkill node for Bluetooth on " Aurelien Jarno
2026-08-31 4:44 ` Aurelien Jarno
2026-08-31 4:44 ` [PATCH v3 4/5] riscv: dts: spacemit: k3: add rfkill node for WLAN on the K3 " Aurelien Jarno
2026-08-31 4:44 ` Aurelien Jarno
2026-08-31 4:44 ` [PATCH v3 5/5] riscv64: defconfig: Enable BT and WLAN support for SpacemiT " Aurelien Jarno
-- strict thread matches above, loose matches on Subject: below --
2026-08-19 16:15 [PATCH v3 0/5] Enable Bluetooth and WiFi on K3 Pico ITX Aurelien Jarno
2026-08-19 16:15 ` [PATCH v3 1/5] riscv: dts: spacemit: k3: move USB3 phy to board level Aurelien Jarno
2026-08-19 16:15 ` Aurelien Jarno
2026-08-22 2:17 ` Inochi Amaoto
2026-08-22 2:17 ` Inochi Amaoto
2026-08-22 9:37 ` Aurelien Jarno
2026-08-22 9:37 ` Aurelien Jarno
2026-08-22 12:33 ` Inochi Amaoto
2026-08-22 12:33 ` Inochi Amaoto
2026-08-22 13:37 ` Aurelien Jarno
2026-08-22 13:37 ` Aurelien Jarno
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=20260831045448.58B591F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=aurelien@aurel32.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.