From: sashiko-bot@kernel.org
To: "Elson Serrao" <elson.serrao@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v7 1/8] dt-bindings: soc: qcom: eud: Add per-path child nodes for UTMI routing
Date: Mon, 31 Aug 2026 03:09:55 +0000 [thread overview]
Message-ID: <20260831030956.470BB1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260831030147.1500616-2-elson.serrao@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing `#address-cells` and `#size-cells` in the `required` list of conditional blocks for configurations that use child nodes with unit addresses (`eud-path@X`).
--
commit 4ec64fc010ea8502aae975163886af215d1fa042
Author: Elson Serrao <elson.serrao@oss.qualcomm.com>
dt-bindings: soc: qcom: eud: Add per-path child nodes for UTMI routing
This commit modifies the EUD binding to model UTMI paths as separate child
nodes (eud-path@X) with their own OF graph, replacing the flattened ports
representation. It introduces the qcom,sm8350-eud compatible for dual-path
topologies and conditionally maintains legacy support for sc7280.
> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml
> index 84218636c0d8d..c377a77d623cf 100644
> --- a/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml
> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml
[ ... ]
> @@ -45,10 +46,88 @@ properties:
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: qcom,sc7280-eud
> + then:
> + oneOf:
> + - required:
> + - ports
> + properties:
> + eud-path@0: false
> + eud-path@1: false
> + - required:
> + - eud-path@0
[Severity: Low]
Does this configuration need to require #address-cells and #size-cells
for the parent node?
Since the eud-path@0 child node has a unit address, failing to mandate
the cell size properties in this branch allows configurations to omit them,
passing schema validation silently even though the structure is invalid.
> + properties:
> + ports: false
> + eud-path@1: false
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: qcom,sm8350-eud
> + then:
> + required:
> + - eud-path@0
> + - eud-path@1
[Severity: Low]
Should this branch also explicitly require #address-cells and #size-cells?
Similar to the sc7280 case above, the sm8350 variant strictly requires child
nodes with unit addresses. Without mandating the cell size properties in the
required list, a device tree could miss them and still pass YAML validation.
> + properties:
> + ports: false
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260831030147.1500616-1-elson.serrao@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-08-31 3:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 3:01 [PATCH v7 0/8] Improve Qualcomm EUD driver and platform support Elson Serrao
2026-08-31 3:01 ` [PATCH v7 1/8] dt-bindings: soc: qcom: eud: Add per-path child nodes for UTMI routing Elson Serrao
2026-08-31 3:09 ` sashiko-bot [this message]
2026-08-31 22:39 ` Bjorn Andersson
2026-08-31 3:01 ` [PATCH v7 2/8] usb: misc: qcom_eud: add sysfs attribute for port selection Elson Serrao
2026-08-31 3:12 ` sashiko-bot
2026-08-31 3:01 ` [PATCH v7 3/8] usb: misc: qcom_eud: add per-path High-Speed PHY control Elson Serrao
2026-08-31 3:15 ` sashiko-bot
2026-08-31 3:01 ` [PATCH v7 4/8] usb: misc: qcom_eud: add per-path role switch support Elson Serrao
2026-08-31 3:17 ` sashiko-bot
2026-08-31 3:01 ` [PATCH v7 5/8] usb: misc: qcom_eud: improve enable_store API Elson Serrao
2026-08-31 3:13 ` sashiko-bot
2026-08-31 3:01 ` [PATCH v7 6/8] usb: misc: qcom_eud: add role-based EUD control Elson Serrao
2026-08-31 3:13 ` sashiko-bot
2026-09-01 11:36 ` Konrad Dybcio
2026-09-10 1:37 ` Elson Serrao
2026-08-31 3:01 ` [PATCH v7 7/8] usb: misc: qcom_eud: fix virtual attach/detach event handling Elson Serrao
2026-08-31 3:17 ` sashiko-bot
2026-08-31 3:01 ` [PATCH v7 8/8] arm64: dts: qcom: kodiak: Desribe EUD UTMI routing and connector mapping Elson Serrao
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=20260831030956.470BB1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=elson.serrao@oss.qualcomm.com \
--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.