Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Stanislav Zaikin" <zstaseg@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: soc: qcom: add xiaomi,taoyao-pmic-glink compatible
Date: Tue, 15 Sep 2026 08:58:39 +0000	[thread overview]
Message-ID: <20260915085840.21EAD1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260915084901.56622-2-zstaseg@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: mutually exclusive board and SoC compatible strings
--

commit c55f57a1517ca9ce82e67923ff8313d8fc20239f
Author: Stanislav Zaikin <zstaseg@gmail.com>

dt-bindings: soc: qcom: add xiaomi,taoyao-pmic-glink compatible

This commit adds the xiaomi,taoyao-pmic-glink compatible string for the
Xiaomi 12 Lite 5G to the pmic-glink binding.

> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,pmic-glink.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,pmic-glink.yaml
> index 16ad4f5698fc3..8ca057c4e3e61 100644
> --- a/Documentation/devicetree/bindings/soc/qcom/qcom,pmic-glink.yaml
> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,pmic-glink.yaml
> @@ -41,6 +41,7 @@ properties:
>        - items:
>            - enum:
>                - qcom,sm7325-pmic-glink
> +              - xiaomi,taoyao-pmic-glink
>            - const: qcom,qcm6490-pmic-glink
>            - const: qcom,pmic-glink

[Severity: Low]
Does this force the compatible strings to be mutually exclusive and limit the
fallback chain to exactly 3 items?

Standard Device Tree design dictates that compatible strings should be ordered
from most-specific (board) to least-specific (SoC, generic). A board-specific
compatible string for a subsystem should fall back to the SoC-specific string if
they share the same underlying hardware.

By adding xiaomi,taoyao-pmic-glink to the same enum as qcom,sm7325-pmic-glink
in a 3-item list, the schema forces the DT author to choose one or the other,
preventing a complete fallback chain.

As a result, the DT is forced to drop the qcom,sm7325-pmic-glink fallback
string to pass schema validation. This breaks the standard DT fallback chain.

Should the schema instead define a separate 4-item list under oneOf to enforce
the board string, followed by the SoC string, followed by the base fallbacks?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260915084901.56622-1-zstaseg@gmail.com?part=1

  reply	other threads:[~2026-09-15  8:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  8:48 [PATCH v4 0/3] Add Xiaomi 12 Lite 5G (taoyao) battery support Stanislav Zaikin
2026-09-15  8:48 ` [PATCH v4 1/3] dt-bindings: soc: qcom: add xiaomi,taoyao-pmic-glink compatible Stanislav Zaikin
2026-09-15  8:58   ` sashiko-bot [this message]
2026-09-17 10:07   ` Krzysztof Kozlowski
2026-09-18  7:54     ` Stanislav Zaikin
2026-09-15  8:49 ` [PATCH v4 2/3] power: supply: qcom_battmgr: add Xiaomi taoyao support Stanislav Zaikin
2026-09-15  8:49 ` [PATCH v4 3/3] arm64: dts: qcom: sm7325-xiaomi-taoyao: switch to device-specific pmic-glink compatible Stanislav Zaikin
2026-09-17 11:31   ` Konrad Dybcio
2026-09-18 11:29     ` Stanislav Zaikin

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=20260915085840.21EAD1F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=zstaseg@gmail.com \
    /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