From: Rob Herring <robh@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: devicetree@vger.kernel.org, lee@kernel.org, mfd@lists.linux.dev,
conor+dt@kernel.org
Subject: Re: [PATCH] dt-bindings: mfd: hisilicon: Fix Hi6421 SPMI compatible
Date: Wed, 23 Sep 2026 11:33:31 -0500 [thread overview]
Message-ID: <20260923163331.GJ27237-robh@kernel.org> (raw)
In-Reply-To: <20260921233651.591281F000FF@smtp.kernel.org>
On Mon, Sep 21, 2026 at 11:36:50PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] dt-bindings: mfd: hi6421: invalid gpios property for interrupt line
> --
>
> commit 4ce4ba18007f2f81249a1f2307d744174beb3e75
> Author: Rob Herring (Arm) <robh@kernel.org>
>
> dt-bindings: mfd: hisilicon: Fix Hi6421 SPMI compatible
>
> This commit updates the device tree binding for the Hi6421 SPMI PMIC to use
> the hisilicon,hi6421-spmi compatible string. It also allows the gpios
> property for the GPIO interrupt line used by the HiKey970 PMIC node.
>
> > diff --git a/Documentation/devicetree/bindings/mfd/hisilicon,hi6421-spmi-pmic.yaml b/Documentation/devicetree/bindings/mfd/hisilicon,hi6421-spmi-pmic.yaml
> > index 6a824351834ee..9275c561e9d49 100644
> > --- a/Documentation/devicetree/bindings/mfd/hisilicon,hi6421-spmi-pmic.yaml
> > +++ b/Documentation/devicetree/bindings/mfd/hisilicon,hi6421-spmi-pmic.yaml
> [ ... ]
> > @@ -32,6 +32,9 @@ properties:
> > '#interrupt-cells':
> > const: 2
> >
> > + gpios:
> > + maxItems: 1
> > +
>
> [Severity: Medium]
> Does this property legitimize a broken device tree description by using gpios
> for an interrupt line?
>
> Looking at the driver in hi6421v600_irq_probe(), it unconditionally relies on
> platform_get_irq() to fetch its interrupt:
>
> drivers/misc/hi6421v600-irq.c:hi6421v600_irq_probe() {
> ...
> priv->irq = platform_get_irq(pmic_pdev, 0);
> if (priv->irq < 0)
> return priv->irq;
> ...
> }
>
> Because platform_get_irq() only parses the "interrupts" property, it lacks a
> fallback to parse "gpios". Will this cause the driver to fail to probe when
> using the HiKey970 PMIC node configuration since it cannot find the interrupt?
The staging driver used 'gpios'. That was moved to interrupts, so the
gpios hunk can be dropped. And then the .dts needs to be updated.
Rob
prev parent reply other threads:[~2026-09-23 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 23:26 [PATCH] dt-bindings: mfd: hisilicon: Fix Hi6421 SPMI compatible Rob Herring (Arm)
2026-09-21 23:36 ` sashiko-bot
2026-09-23 16:33 ` Rob Herring [this message]
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=20260923163331.GJ27237-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=mfd@lists.linux.dev \
--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