linux-kernel - Re: [PATCH] gpio/rockchip: lock GPIOs used as interrupts

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: <9812574.z3kqYUtTCC@archbook>
Date:   Thu, 02 Dec 2021 17:45:49 +0100
From:   Nicolas Frattaroli <frattaroli.nicolas@...il.com>
To:     linux-gpio@...r.kernel.org, linux-rockchip@...ts.infradead.org
Cc:     John Keeping <john@...anate.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Bartosz Golaszewski <brgl@...ev.pl>,
        Heiko Stuebner <heiko@...ech.de>,
        linux-arm-kernel@...ts.infradead.org,
        linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
        John Keeping <john@...anate.com>
Subject: Re: [PATCH] gpio/rockchip: lock GPIOs used as interrupts

On Donnerstag, 2. Dezember 2021 16:50:21 CET John Keeping wrote:
> Use the standard gpiochip request/release resource functions so that any
> GPIOs used as interrupts are properly locked.  This allows libgpiod to
> correctly show these GPIOs as in-use.
> 
> Signed-off-by: John Keeping <john@...anate.com>

Tested-by: Nicolas Frattaroli <frattaroli.nicolas@...il.com>

Applied this on my Quartz64 Model A (RK3566) where I currently am
having a play with some SPI devices. Now gpioinfo correctly shows
the interrupt pin as being in use.

Before:
         line   3:      unnamed       unused   input  active-high 

After:
         line   3:      unnamed  "interrupt"   input  active-high [used]

Regards,
Nicolas Frattaroli