Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Alexey Charkov" <alchark@flipper.net>
Cc: mfd@lists.linux.dev, robh@kernel.org, conor+dt@kernel.org,
	lee@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mfd: ti,bq25703a: Expand to include BQ25798
Date: Mon, 14 Sep 2026 14:08:20 +0000	[thread overview]
Message-ID: <20260914140821.269AC1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260914-bq25798-v1-1-dc5e2ec343c4@flipper.net>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Adding an array-based fallback compatible string without updating the `if: properties: compatible: const:` conditionals causes the new compatible to bypass device-specific schema constraints.
--

commit 37d04d6cb52639a3cc4ba9ade1878fa540a5cb3e
Author: Alexey Charkov <alchark@flipper.net>

dt-bindings: mfd: ti,bq25703a: Expand to include BQ25798

TI has unpublished the BQ25792 charger variant and pulled its docs from
their website. BQ25798 is a pin and register compatible replacement. Expand
the existing binding to include BQ25798 with a fallback compatible to
BQ25792.

Link: https://www.ti.com/product/BQ25798

> diff --git a/Documentation/devicetree/bindings/mfd/ti,bq25703a.yaml b/Documentation/devicetree/bindings/mfd/ti,bq25703a.yaml
> index cdce83f058041..43afd232a6142 100644
> --- a/Documentation/devicetree/bindings/mfd/ti,bq25703a.yaml
> +++ b/Documentation/devicetree/bindings/mfd/ti,bq25703a.yaml
> @@ -11,9 +11,14 @@ maintainers:
>  
>  properties:
>    compatible:
> -    enum:
> -      - ti,bq25703a
> -      - ti,bq25792
> +    oneOf:
> +      - enum:
> +          - ti,bq25703a
> +          - ti,bq25792
> +      - items:
> +          - enum:
> +              - ti,bq25798
> +          - const: ti,bq25792

[Severity: Medium]
Is this a regression that causes the new compatible string to bypass
device-specific schema constraints?

Later in the file's allOf/if section, there is an exact match condition
for the ti,bq25792 compatible string:

  - if:
      properties:
        compatible:
          const: ti,bq25792

Since the schema const keyword mandates strict equality, it will fail to
match the fallback array ["ti,bq25798", "ti,bq25792"]. As a result, if a
devicetree author specifies compatible = "ti,bq25798", "ti,bq25792" and
configures out-of-bounds regulator or current values, the device-specific
hardware constraints for ti,bq25792 will not be applied during validation.

Could this if condition be updated to use contains instead of const, or
otherwise include the new fallback array?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260914-bq25798-v1-1-dc5e2ec343c4@flipper.net?part=1

  reply	other threads:[~2026-09-14 14:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 13:48 [PATCH] dt-bindings: mfd: ti,bq25703a: Expand to include BQ25798 Alexey Charkov
2026-09-14 14:08 ` sashiko-bot [this message]
2026-09-14 14:26   ` Alexey Charkov

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=20260914140821.269AC1F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=alchark@flipper.net \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lee@kernel.org \
    --cc=mfd@lists.linux.dev \
    --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