linux-kernel - Re: [PATCH] dt-bindings: mfd: Correct interrupt flags in examples

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]

Date:   Wed, 9 Sep 2020 10:17:16 +0200
From:   "krzk@...nel.org" <krzk@...nel.org>
To:     "Vaittinen, Matti" <Matti.Vaittinen@...rohmeurope.com>
Cc:     "lee.jones@...aro.org" <lee.jones@...aro.org>,
        linux-power <linux-power@...rohmeurope.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "tharvey@...eworks.com" <tharvey@...eworks.com>,
        "rjones@...eworks.com" <rjones@...eworks.com>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>
Subject: Re: [PATCH] dt-bindings: mfd: Correct interrupt flags in examples

On Wed, Sep 09, 2020 at 06:30:44AM +0000, Vaittinen, Matti wrote:
> 
> On Tue, 2020-09-08 at 16:59 +0200, Krzysztof Kozlowski wrote:
> > GPIO_ACTIVE_x flags are not correct in the context of interrupt
> > flags.
> > These are simple defines so they could be used in DTS but they will
> > not
> > have the same meaning:
> > 1. GPIO_ACTIVE_HIGH = 0 = IRQ_TYPE_NONE
> > 2. GPIO_ACTIVE_LOW  = 1 = IRQ_TYPE_EDGE_RISING
> > 
> > Correct the interrupt flags, assuming the author of the code wanted
> > some
> > logical behavior behind the name "ACTIVE_xxx", this is:
> >   ACTIVE_LOW => IRQ_TYPE_LEVEL_LOW
> > 
> > Signed-off-by: Krzysztof Kozlowski <krzk@...nel.org>
> 
> For BD70528:
> Acked-By: Matti Vaittinen <matti.vaittinen@...rohmeurope.com>
> 
> > ---
> >  Documentation/devicetree/bindings/mfd/act8945a.txt          | 2 +-
> >  Documentation/devicetree/bindings/mfd/gateworks-gsc.yaml    | 3 ++-
> >  Documentation/devicetree/bindings/mfd/rohm,bd70528-pmic.txt | 2 +-
> >  3 files changed, 4 insertions(+), 3 deletions(-)
> > 
> > 
> > diff --git a/Documentation/devicetree/bindings/mfd/rohm,bd70528-
> > pmic.txt b/Documentation/devicetree/bindings/mfd/rohm,bd70528-
> > pmic.txt
> > index c3c02ce73cde..386eec06cf08 100644
> > --- a/Documentation/devicetree/bindings/mfd/rohm,bd70528-pmic.txt
> > +++ b/Documentation/devicetree/bindings/mfd/rohm,bd70528-pmic.txt
> > @@ -39,7 +39,7 @@ pmic: pmic@4b {
> >  	compatible = "rohm,bd70528";
> >  	reg = <0x4b>;
> >  	interrupt-parent = <&gpio1>;
> > -	interrupts = <29 GPIO_ACTIVE_LOW>;
> > +	interrupts = <29 IRQ_TYPE_LEVEL_LOW>;
> 
> This is how it should have been from the beginning :) Thanks!

I start to wonder now. It seems some boards do not configure a pull up
there, so IRQ_TYPE_LEVEL_LOW is wrong - causes the line to stay in low
state.  But actually this maybe is a problem of missing pull up, not the
IRQ flag?

Best regards,
Krzysztof