All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Stanislav Zaikin" <zstaseg@gmail.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [RFC PATCH 1/3] dt-bindings: soc: qcom: add xiaomi,taoyao-pmic-glink compatible
Date: Thu, 30 Jul 2026 09:53:07 +0000	[thread overview]
Message-ID: <20260730095308.0D27F1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260730093502.689505-2-zstaseg@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The schema change enforces an incorrect, truncated fallback chain that skips the intermediate SoC compatible string.
--

--- Patch [1]: [RFC PATCH 1/3] dt-bindings: soc: qcom: add xiaomi,taoyao-pmic-glink compatible ---
commit 52fb33657926ca90fb558df9e2cd09cb2c215e6e
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. This allows its battery manager to be matched to a
device-specific variant in qcom_battmgr.

> 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: Medium]
Does this schema change enforce an incorrect, truncated fallback chain that
skips the intermediate SoC compatible string?

By grouping the board-specific string (xiaomi,taoyao-pmic-glink) in an enum
alongside the SoC string (qcom,sm7325-pmic-glink), the schema restricts the
compatible list to exactly 3 items. This forces device tree authors to omit
the SoC-level fallback (qcom,sm7325-pmic-glink) in order to pass dtbs_check.

Should this instead be defined with a 4-item list so the board compatible
can properly fall back to the sm7325 SoC compatible before falling back to
the generic qcm6490 and pmic-glink ones?

>        - items:

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

  reply	other threads:[~2026-07-30  9:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30  9:34 [RFC PATCH 0/3] Add Xiaomi 12 Lite 5G (taoyao) battery support Stanislav Zaikin
2026-07-30  9:35 ` [RFC PATCH 1/3] dt-bindings: soc: qcom: add xiaomi,taoyao-pmic-glink compatible Stanislav Zaikin
2026-07-30  9:53   ` sashiko-bot [this message]
2026-07-30  9:35 ` [RFC PATCH 2/3] power: supply: qcom_battmgr: add Xiaomi taoyao support Stanislav Zaikin
2026-07-30  9:35 ` [RFC PATCH 3/3] arm64: dts: qcom: sm7325-xiaomi-taoyao: switch to device-specific pmic-glink compatible 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=20260730095308.0D27F1F000E9@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 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.