From: sashiko-bot@kernel.org
To: "Faisal Hassan" <faisal.hassan@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 3/7] dt-bindings: usb: Add qcom,sa8255p-dwc3 for firmware-managed resources
Date: Thu, 03 Sep 2026 15:56:13 +0000 [thread overview]
Message-ID: <20260903155613.C6AB71F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260903153827.3463313-4-faisal.hassan@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The 'dma-coherent' property is missing from the binding, preventing it from being used in device trees.
- [Low] The 'interrupt-names' property lacks item constraints (e.g., 'items' or 'enum' lists), allowing arbitrary strings (like typos) to pass validation.
--
commit 5d3262b4959573620da7ce43d432ab2890209041
Author: Faisal Hassan <faisal.hassan@oss.qualcomm.com>
dt-bindings: usb: Add qcom,sa8255p-dwc3 for firmware-managed resources
This commit adds a new device tree binding for the USB controller on the
Qualcomm SA8255P automotive SoC. It specifies that platform resources
such as clocks and interconnects are abstracted and managed collectively by
firmware through two power domains.
> diff --git a/Documentation/devicetree/bindings/usb/qcom,sa8255p-dwc3.yaml b/Documentation/devicetree/bindings/usb/qcom,sa8255p-dwc3.yaml
> new file mode 100644
> index 0000000000000..c6db7bcf4981e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/qcom,sa8255p-dwc3.yaml
[ ... ]
> + interrupts:
> + minItems: 1
> + maxItems: 6
> +
> + interrupt-names:
> + minItems: 1
> + maxItems: 6
[Severity: Low]
Does interrupt-names need an items list or enum to constrain the exact string
names?
Without an explicit list, the schema will accept any arbitrary strings, which
prevents dtbs_check from catching typos during validation.
[ ... ]
> +allOf:
> + - $ref: snps,dwc3-common.yaml#
> +
> +unevaluatedProperties: false
[Severity: Medium]
Since unevaluatedProperties is false, does dma-coherent need to be explicitly
defined in this binding?
Because dma-coherent is omitted here and in the referenced
snps,dwc3-common.yaml, adding it to a device tree will cause dtbs_check
validation to fail.
If device tree authors omit the property to appease the validator, could the
kernel fall back to non-coherent DMA mappings, resulting in unnecessary cache
maintenance overhead and a performance regression on coherent hardware?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260903153827.3463313-1-faisal.hassan@oss.qualcomm.com?part=3
next prev parent reply other threads:[~2026-09-03 15:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 15:38 [PATCH v2 0/7] usb: dwc3: qcom: Add firmware-managed resource support for SA8255P Faisal Hassan
2026-09-03 15:38 ` [PATCH v2 1/7] usb: dwc3: qcom: re-enable wakeup interrupts on failed resume Faisal Hassan
2026-09-03 15:53 ` sashiko-bot
2026-09-11 23:48 ` Thinh Nguyen
2026-09-03 15:38 ` [PATCH v2 2/7] usb: dwc3: qcom: Distinguish PM and runtime suspend/resume paths Faisal Hassan
2026-09-11 23:51 ` Thinh Nguyen
2026-09-03 15:38 ` [PATCH v2 3/7] dt-bindings: usb: Add qcom,sa8255p-dwc3 for firmware-managed resources Faisal Hassan
2026-09-03 15:56 ` sashiko-bot [this message]
2026-09-07 9:08 ` Krzysztof Kozlowski
2026-09-03 15:38 ` [PATCH v2 4/7] usb: host: xhci-plat: Support XHCI_RESET_ON_RESUME via device property Faisal Hassan
2026-09-03 15:38 ` [PATCH v2 5/7] usb: dwc3: add xhci-reset-on-resume property for power-loss resume Faisal Hassan
2026-09-03 16:08 ` sashiko-bot
2026-09-04 6:09 ` Krishna Kurapati
2026-09-12 1:03 ` Thinh Nguyen
2026-09-03 15:38 ` [PATCH v2 6/7] usb: dwc3: qcom: Support broken suspend for SA8255P Faisal Hassan
2026-09-03 16:13 ` sashiko-bot
2026-09-12 1:24 ` Thinh Nguyen
2026-09-03 15:38 ` [PATCH v2 7/7] usb: dwc3: qcom: Support firmware-managed resource states for power management Faisal Hassan
2026-09-03 16:14 ` sashiko-bot
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=20260903155613.C6AB71F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=faisal.hassan@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.