From: sashiko-bot@kernel.org
To: "Qiang Yu" <qiang.yu@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v9 1/7] dt-bindings: clock: qcom: Move glymur TCSR to own binding
Date: Tue, 14 Jul 2026 05:09:53 +0000 [thread overview]
Message-ID: <20260714050953.BACC51F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260713-tcsr_qref_0714-v9-1-373670ab15f9@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The newly added qcom,glymur-tcsr.yaml binding marks 17 `vdda-qref*` supply properties as unconditionally required, but existing device trees do not provide them, causing a `dtbs_check` validation regression.
--
--- Patch [1]: [PATCH v9 1/7] dt-bindings: clock: qcom: Move glymur TCSR to own binding ---
commit 6bffb0197809346112dba264dc91035d8e1ed982
Author: Qiang Yu <qiang.yu@oss.qualcomm.com>
dt-bindings: clock: qcom: Move glymur TCSR to own binding
This commit extracts the Glymur TCSR block into its own dedicated YAML binding
file and documents the supply properties required by the QREF block. It uses
an allOf conditional block to enforce these supplies for the qcom,glymur-tcsr
compatible string.
> diff --git a/Documentation/devicetree/bindings/clock/qcom,glymur-tcsr.yaml b/Documentation/devicetree/bindings/clock/qcom,glymur-tcsr.yaml
> new file mode 100644
> index 0000000000000..ec89feff89e4e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/qcom,glymur-tcsr.yaml
[ ... ]
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: qcom,glymur-tcsr
> + then:
> + required:
> + - vdda-qrefrpt0-0p9-supply
> + - vdda-qrefrpt1-0p9-supply
[Severity: Medium]
Does this cause a dtbs_check validation regression for existing platforms?
By marking these 17 vdda-qref* supply properties as unconditionally required
in the allOf block, validation will fail for existing device trees (such as
arch/arm64/boot/dts/qcom/glymur.dtsi) that use the qcom,glymur-tcsr
compatible string but do not yet provide these supplies.
Would it be better to introduce these properties as optional first, or ensure
the corresponding device tree updates are included in the same patch series
to prevent breaking schema validation?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260713-tcsr_qref_0714-v9-0-373670ab15f9@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-07-14 5:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 4:59 [PATCH v9 0/7] clk: qcom: Add common clkref support and migrate Glymur and Mahua Qiang Yu
2026-07-14 4:59 ` [PATCH v9 1/7] dt-bindings: clock: qcom: Move glymur TCSR to own binding Qiang Yu
2026-07-14 5:09 ` sashiko-bot [this message]
2026-07-14 4:59 ` [PATCH v9 2/7] dt-bindings: clock: qcom,glymur-tcsr: Add mahua support Qiang Yu
2026-07-14 5:08 ` sashiko-bot
2026-07-14 4:59 ` [PATCH v9 3/7] clk: qcom: Add generic clkref_en support Qiang Yu
2026-07-14 4:59 ` [PATCH v9 4/7] clk: qcom: tcsrcc-glymur: Add regulator supplies and migrate to clk_ref helper Qiang Yu
2026-07-14 4:59 ` [PATCH v9 5/7] clk: qcom: tcsrcc-glymur: Add Mahua QREF regulator support Qiang Yu
2026-07-14 4:59 ` [PATCH v9 6/7] arm64: dts: qcom: glymur: Add QREF regulator supplies to TCSR Qiang Yu
2026-07-14 4:59 ` [PATCH v9 7/7] arm64: dts: qcom: mahua: " Qiang Yu
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=20260714050953.BACC51F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=qiang.yu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox