ARM Sunxi Platform Development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jerome Brunet" <jbrunet@baylibre.com>
Cc: linux-sunxi@lists.linux.dev, conor+dt@kernel.org,
	robh@kernel.org, mfd@lists.linux.dev, lee@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v7 3/5] dt-bindings: mfd: x-powers,axp152: Document AXP318W
Date: Thu, 10 Sep 2026 09:42:51 +0000	[thread overview]
Message-ID: <20260910094251.A112A1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260910-axp318-regulator-v7-3-de720ceb9bac@baylibre.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The new `x-powers,axp318w` compatible string is omitted from the conditional block that makes the `interrupts` property optional for recent generation PMICs.
--

commit e4119d6ce87c67baf660bd6f040790fb69b77af3
Author: Andre Przywara <andre.przywara@arm.com>

dt-bindings: mfd: x-powers,axp152: Document AXP318W

This commit adds the compatible string x-powers,axp318w for the AXP318W PMIC
to the binding schema. It also adds new input supply properties and updates
the regex for matching switched output nodes.

> diff --git a/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml b/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml
> index 45f015d63df16..38556c32417b3 100644
> --- a/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml
> +++ b/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml
> @@ -83,6 +83,7 @@ allOf:
>            contains:
>              enum:
>                - x-powers,axp313a
> +              - x-powers,axp318w
>                - x-powers,axp323
>                - x-powers,axp15060
>                - x-powers,axp717

[Severity: Medium]
Does the x-powers,axp318w compatible string also need to be added to the
earlier if-then block that governs the interrupts requirement?

Just above this hunk in Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml,
there is a block that makes interrupts mandatory for all PMICs except a select
few:

  - if:
      not:
        properties:
          compatible:
            contains:
              enum:
                - x-powers,axp15060
                - x-powers,axp305
                - x-powers,axp313a
                - x-powers,axp323

    then:
      required:
        - interrupts

By omitting x-powers,axp318w from this enum, the interrupts property is
mandatory for the new PMIC. Could this cause device trees with an unconnected
AXP318W interrupt line to falsely fail dt_binding_check validation, given that
similar recent generation PMICs operate fine without it?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260910-axp318-regulator-v7-0-de720ceb9bac@baylibre.com?part=3

  reply	other threads:[~2026-09-10  9:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10  9:31 [PATCH v7 0/5] regulator: Add X-Powers AXP318W PMIC support Jerome Brunet
2026-09-10  9:31 ` [PATCH v7 1/5] mfd: axp20x: Constify axp313 and axp717 cells Jerome Brunet
2026-09-10  9:34   ` sashiko-bot
2026-09-10  9:31 ` [PATCH v7 2/5] mfd: axp20x-i2c: Fix i2c instantiation Jerome Brunet
2026-09-10  9:40   ` sashiko-bot
2026-09-10  9:31 ` [PATCH v7 3/5] dt-bindings: mfd: x-powers,axp152: Document AXP318W Jerome Brunet
2026-09-10  9:42   ` sashiko-bot [this message]
2026-09-10 10:37     ` Jerome Brunet
2026-09-10  9:31 ` [PATCH v7 4/5] mfd: axp20x: Add support for AXP318W PMIC Jerome Brunet
2026-09-10  9:40   ` sashiko-bot
2026-09-10  9:31 ` [PATCH v7 5/5] regulator: axp20x: add support for the AXP318W Jerome Brunet
2026-09-10  9:39   ` sashiko-bot

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=20260910094251.A112A1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=lee@kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --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