linux-kernel - Re: [PATCH] dt-bindings: mfd: x-powers,axp152: make interrupt optional for more chips

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230805235030.35bed33c@slackpad.lan>
Date:   Sat, 5 Aug 2023 23:50:30 +0100
From:   Andre Przywara <andre.przywara@....com>
To:     Shengyu Qu <wiagn233@...look.com>
Cc:     Lee Jones <lee@...nel.org>, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Chen-Yu Tsai <wens@...e.org>, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, Icenowy Zheng <uwu@...nowy.me>,
        Martin Botka <martin.botka@...ainline.org>,
        Martin Botka <martin@...u3d.com>,
        Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH] dt-bindings: mfd: x-powers,axp152: make interrupt
 optional for more chips

On Sat, 5 Aug 2023 23:43:35 +0800
Shengyu Qu <wiagn233@...look.com> wrote:

Hi Shengyu,

> No, you can't only add the binding stuff. The PEK driver would crash when
> there's no IRQ config in dts.

Well, that's strictly speaking a problem of the existing Linux driver
then, which cannot cope with this new updated binding yet. But the
binding needs to be updated first in any case, so this patch needs
to come first.

But yeah, indeed this is missing the extension of the "IRQ > 0"  check
from the 15060 MFD code, I will send a patch shortly to extend this to
the AXP305 and AXP313a.

Thanks for the heads up!

Cheers,
Andre

> Best regards,
> 
> Shengyu
> 
> > All X-Powers PMICs described by this binding have an IRQ pin, and so
> > far (almost) all boards connected this to some NMI pin or GPIO on the SoC
> > they are connected to.
> > However we start to see boards that omit this connection, and technically
> > the IRQ pin is not essential to the basic PMIC operation.
> > The existing Linux driver allows skipping an IRQ pin setup for some
> > chips already, so update the binding to also make the DT property
> > optional for these chips, so that we can actually have DTs describing
> > boards with the PMIC interrupt not wired up.
> >
> > Signed-off-by: Andre Przywara <andre.przywara@....com>
> > ---
> > Hi,
> >
> > arguably the IRQ functionality is optional for many more PMICs,
> > especially if a board doesn't use GPIOs or a power key.
> > So I wonder if the interrupts property should become optional for all?
> > After all it's more a board designer's decision to wire up the IRQ pin
> > or not, and nothing that's really related to a particular PMIC.
> >
> > Cheers,
> > Andre
> >
> >   Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml | 5 ++++-
> >   1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml b/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml
> > index 9ad55746133b5..06f1779835a1e 100644
> > --- a/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml
> > +++ b/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml
> > @@ -67,7 +67,10 @@ allOf:
> >           properties:
> >             compatible:
> >               contains:
> > -              const: x-powers,axp305
> > +              enum:
> > +                - x-powers,axp15060
> > +                - x-powers,axp305
> > +                - x-powers,axp313a
> >   
> >       then:
> >         required: