From:   Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
To:     linux-gpio@vger.kernel.org, linux-rockchip@lists.infradead.org
Cc:     John Keeping <john@metanate.com>,
        Linus Walleij <linus.walleij@linaro.org>,
        Bartosz Golaszewski <brgl@bgdev.pl>,
        Heiko Stuebner <heiko@sntech.de>,
        linux-arm-kernel@lists.infradead.org,
        linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
        John Keeping <john@metanate.com>
Subject: Re: [PATCH] gpio/rockchip: lock GPIOs used as interrupts
Date:   Thu, 02 Dec 2021 17:45:49 +0100
Message-ID: <9812574.z3kqYUtTCC@archbook>
In-Reply-To: <20211202155022.2972779-1-john@metanate.com>
References: <20211202155022.2972779-1-john@metanate.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

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@metanate.com>

Tested-by: Nicolas Frattaroli <frattaroli.nicolas@gmail.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