Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: Frank.Li@oss.nxp.com
Cc: lee@kernel.org, devicetree@vger.kernel.org, mfd@lists.linux.dev,
	Frank.Li@kernel.org, conor+dt@kernel.org, robh@kernel.org,
	imx@lists.linux.dev
Subject: Re: [PATCH 1/1] dt-bindings: mfd: da9052: allow dlg,da9053-aa fallback to dlg,da9052
Date: Mon, 31 Aug 2026 21:41:52 +0000	[thread overview]
Message-ID: <20260831214152.E00371F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260831201522.51294-1-Frank.Li@oss.nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch introduces an inconsistency by explicitly allowing the legacy fallback compatible string `dlg,da9053-aa` with `dlg,da9052`, but omitting `dlg,da9053` which uses the exact same pattern.
--

commit abd213140dc2339cb1dfe32c3ccb7bfd92c4ba9b
Author: Frank Li <Frank.Li@nxp.com>

dt-bindings: mfd: da9052: allow dlg,da9053-aa fallback to dlg,da9052

This patch adds a fallback compatible string schema allowing dlg,da9053-aa to
fall back to dlg,da9052 in order to resolve a legacy platform check_dtbs
warning.

> diff --git a/Documentation/devicetree/bindings/mfd/dlg,da9052.yaml b/Documentation/devicetree/bindings/mfd/dlg,da9052.yaml
> index 1103a8cc5cea4..d1d23c7c4d0c2 100644
> --- a/Documentation/devicetree/bindings/mfd/dlg,da9052.yaml
> +++ b/Documentation/devicetree/bindings/mfd/dlg,da9052.yaml
> @@ -18,6 +18,10 @@ properties:
>            - dlg,da9053-bb
>            - dlg,da9053-bc
>            - dlg,da9052
> +      - items:
> +          - enum:
> +              - dlg,da9053-aa
> +          - const: dlg,da9052

[Severity: Low]
Does this fallback allowance also need to include the plain dlg,da9053 variant
to completely fix the warnings?

Looking at arch/arm/boot/dts/nxp/imx/imx53-smd.dts, the pmic node still
relies on the missing fallback pattern:

		compatible = "dlg,da9053", "dlg,da9052";

Without including dlg,da9053 in the enum alongside dlg,da9053-aa, won't
the legacy device tree node continue to generate a dtbs_check warning?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260831201522.51294-1-Frank.Li@oss.nxp.com?part=1

  reply	other threads:[~2026-08-31 21:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31 20:15 [PATCH 1/1] dt-bindings: mfd: da9052: allow dlg,da9053-aa fallback to dlg,da9052 Frank.Li
2026-08-31 21:41 ` sashiko-bot [this message]
2026-09-01 17:00 ` Conor Dooley
2026-09-02 10:25   ` Lee Jones
2026-09-02 17:01     ` Conor Dooley
2026-09-03  9:06       ` Lee Jones
2026-09-03 10:06         ` Krzysztof Kozlowski
2026-09-03 11:36           ` Lee Jones
2026-09-03 10:04   ` Krzysztof Kozlowski
2026-09-03 15:34     ` Conor Dooley
2026-09-03 19:15     ` Frank Li
2026-09-03  9:58 ` Krzysztof Kozlowski
2026-09-03 19:22   ` Frank Li

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=20260831214152.E00371F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.Li@oss.nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --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