Linux Input/HID development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Luca Leonardo Scorcia" <l.scorcia@gmail.com>
Cc: devicetree@vger.kernel.org, linux-input@vger.kernel.org,
	conor+dt@kernel.org, dmitry.torokhov@gmail.com, robh@kernel.org
Subject: Re: [PATCH v6 1/7] dt-bindings: mfd: mt6397: Add MT6392 PMIC
Date: Fri, 12 Jun 2026 20:37:34 +0000	[thread overview]
Message-ID: <20260612203734.C43DC1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260612200717.361018-2-l.scorcia@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The dt-bindings schema for the MT6392 PMIC omits the 'mediatek,mt6392-regulator' compatible string for the 'regulators' child node. Since the 'regulators' node is unconditionally marked as required in the schema, any complete device tree correctly describing the MT6392 hardware must include it. Omitting the MT6392-specific regulator compatible string from the schema forces DT authors to either write incomplete DTs (which fail validation because the node is required) or use incorrect/generic compatible strings, causing schema validation failures when they attempt to properly describe the hardware with 'mediatek,mt6392-regulator'.
--

commit a20444c8e4c98a81558d6d5c619b650c00235e18
Author: Fabien Parent <parent.f@gmail.com>

dt-bindings: mfd: mt6397: Add MT6392 PMIC

Add the initial bindings for the MT6392 PMIC and its RTC device.

> diff --git a/Documentation/devicetree/bindings/mfd/mediatek,mt6397.yaml b/Documentation/devicetree/bindings/mfd/mediatek,mt6397.yaml
> index 3cbc0dc12c319..e39e81aa99249 100644
> --- a/Documentation/devicetree/bindings/mfd/mediatek,mt6397.yaml
> +++ b/Documentation/devicetree/bindings/mfd/mediatek,mt6397.yaml

[ ... ]

> @@ -72,6 +76,10 @@ properties:
>                - mediatek,mt6331-rtc
>                - mediatek,mt6358-rtc
>                - mediatek,mt6397-rtc
> +          - items:
> +              - enum:
> +                  - mediatek,mt6392-rtc
> +              - const: mediatek,mt6323-rtc

[Severity: Medium]
Should the mediatek,mt6392-regulator compatible string be added to the
regulators child node as well?

Since the regulators node is unconditionally marked as required in the schema,
any complete device tree describing the MT6392 hardware must include it.

Does this missing string cause a regression where DT authors are forced to
either write incomplete DTs (which fail validation) or use incorrect compatible
strings?

This causes schema validation failures when authors attempt to properly describe
the hardware with mediatek,mt6392-regulator:

Documentation/devicetree/bindings/mfd/mediatek,mt6397.yaml:
  regulators:
    ...
    properties:
      compatible:
        oneOf:
          - enum:
              - mediatek,mt6323-regulator
              - mediatek,mt6328-regulator
              ...

>            - items:
>                - enum:
>                    - mediatek,mt6359-rtc

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

  reply	other threads:[~2026-06-12 20:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12 20:04 [PATCH v6 0/7] Add support for MT6392 PMIC Luca Leonardo Scorcia
2026-06-12 20:04 ` [PATCH v6 1/7] dt-bindings: mfd: mt6397: Add " Luca Leonardo Scorcia
2026-06-12 20:37   ` sashiko-bot [this message]
2026-06-12 20:04 ` [PATCH v6 2/7] dt-bindings: input: mtk-pmic-keys: Add MT6392 PMIC keys Luca Leonardo Scorcia
2026-06-12 20:04 ` [PATCH v6 3/7] mfd: mt6397: Use MFD_CELL_* to describe sub-devices Luca Leonardo Scorcia
2026-06-12 20:04 ` [PATCH v6 4/7] mfd: mt6397: Add support for MT6392 PMIC Luca Leonardo Scorcia
2026-06-12 20:44   ` sashiko-bot
2026-06-12 20:04 ` [PATCH v6 5/7] input: keyboard: mtk-pmic-keys: Add MT6392 support Luca Leonardo Scorcia
2026-06-12 20:39   ` sashiko-bot
2026-06-12 20:04 ` [PATCH v6 6/7] pinctrl: mediatek: mt6397: Add MediaTek MT6392 Luca Leonardo Scorcia
2026-06-12 20:04 ` [PATCH v6 7/7] arm64: dts: mediatek: Add MediaTek MT6392 PMIC dtsi Luca Leonardo Scorcia

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=20260612203734.C43DC1F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=l.scorcia@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --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