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 [thread overview]
Message-ID: <9812574.z3kqYUtTCC@archbook> (raw)
In-Reply-To: <20211202155022.2972779-1-john@metanate.com>
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
next prev parent reply other threads:[~2021-12-02 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 15:50 [PATCH] gpio/rockchip: lock GPIOs used as interrupts John Keeping
2021-12-02 16:45 ` Nicolas Frattaroli [this message]
2021-12-03 14:59 ` Bartosz Golaszewski
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=9812574.z3kqYUtTCC@archbook \
--to=frattaroli.nicolas@gmail.com \
--cc=brgl@bgdev.pl \
--cc=heiko@sntech.de \
--cc=john@metanate.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).