From: William Breathitt Gray <wbg@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: William Breathitt Gray <wbg@kernel.org>,
Mark Brown <broonie@kernel.org>,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
Bartosz Golaszewski <brgl@kernel.org>,
linux-kernel@vger.kernel.org, driver-core@lists.linux.dev,
linux-gpio@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Michael Walle <mwalle@kernel.org>,
Yu-Chun Lin <eleanor.lin@realtek.com>,
Fred Eckert <Frede@cmslaser.com>,
Matthew Mohn <matthew.mohn@ishicorp.com>
Subject: Re: [PATCH v1 0/4] gpio: regmap: Keep tracking IRQ requests and releases
Date: Sat, 4 Jul 2026 14:21:19 +0900 [thread overview]
Message-ID: <20260704052120.798323-1-wbg@kernel.org> (raw)
In-Reply-To: <20260702130903.1790633-1-andriy.shevchenko@linux.intel.com>
On Thu, Jul 02, 2026 at 02:42:53PM +0200, Andy Shevchenko wrote:
> During the review of the v3 [1] of the series that adds a driver for
> Realtek DHC RTD1625 SoC GPIO the gap in the GPIO regmap implementation
> has been discovered, id est the IRQ chip that is created by regmap IRQ
> doesn't have IRQ request and release callbacks and hence in terms of
> GPIO does not track if any line is locked as IRQ. This might lead to
> undesired and most likely faulty behaviour. This series is to fill that
> gap. Currently it only fixes the only user of the automatic IRQ chip
> creation facility provided by GPIO regmap, but also provides the exported
> callbacks for others to be possible to call them from customised versions
> of the callbacks in the respective drivers.
>
> Most of the affected drivers if I am not mistaken are the Industrial PC104
> ones, hence I Cc'ed William to look at this and perhaps even test.
Hi Andy,
I'll take a look at these patches when I get a chance. For now, I'll CC
Fred Eckert and Matthew Mohn who have tested these PC104 drivers in the
past and may be interested in this patchset.
Thanks,
William Breathitt Gray
>
> Yu-Chun, can you give a try with your v3 based on this series? I believe
> we can use regmap approach after all.
>
> The merge strategy is to go via GPIO tree with the immutable branch or tag
> provided for the first patch that can be done by regmap tree for others to
> consume. Of course, there are possible options, I'm all ears if you think it
> will be better in any other way.
>
> Link: https://lore.kernel.org/all/20260512033317.1602537-1-eleanor.lin@realtek.com/ [1]
>
> Andy Shevchenko (4):
> regmap-irq: Provide IRQ resource request and release callbacks
> gpio: regmap: Provide default IRQ resource request and release
> callbacks
> gpio: regmap: Apply default resource callbacks for regmap IRQ chip
> gpio: regmap: Order kernel-doc descriptions with the actual appearance
>
> drivers/base/regmap/regmap-irq.c | 22 ++++++++++++++++++++++
> drivers/gpio/gpio-max7360.c | 7 ++++---
> drivers/gpio/gpio-regmap.c | 25 +++++++++++++++++++++++++
> include/linux/gpio/regmap.h | 21 ++++++++++++---------
> include/linux/regmap.h | 2 ++
> 5 files changed, 65 insertions(+), 12 deletions(-)
>
> --
> 2.50.1
>
prev parent reply other threads:[~2026-07-04 5:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 12:42 [PATCH v1 0/4] gpio: regmap: Keep tracking IRQ requests and releases Andy Shevchenko
2026-07-02 12:42 ` [PATCH v1 1/4] regmap-irq: Provide IRQ resource request and release callbacks Andy Shevchenko
2026-07-03 15:29 ` Mark Brown
2026-07-02 12:42 ` [PATCH v1 2/4] gpio: regmap: Provide default " Andy Shevchenko
2026-07-03 11:29 ` Andy Shevchenko
2026-07-02 12:42 ` [PATCH v1 3/4] gpio: regmap: Apply default resource callbacks for regmap IRQ chip Andy Shevchenko
2026-07-03 20:52 ` Linus Walleij
2026-07-02 12:42 ` [PATCH v1 4/4] gpio: regmap: Order kernel-doc descriptions with the actual appearance Andy Shevchenko
2026-07-03 20:51 ` Linus Walleij
2026-07-03 8:17 ` [PATCH v1 0/4] gpio: regmap: Keep tracking IRQ requests and releases Yu-Chun Lin [林祐君]
2026-07-03 8:34 ` Bartosz Golaszewski
2026-07-03 15:29 ` (subset) " Mark Brown
2026-07-04 5:21 ` William Breathitt Gray [this message]
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=20260704052120.798323-1-wbg@kernel.org \
--to=wbg@kernel.org \
--cc=Frede@cmslaser.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@kernel.org \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=eleanor.lin@realtek.com \
--cc=gregkh@linuxfoundation.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=matthew.mohn@ishicorp.com \
--cc=mwalle@kernel.org \
--cc=rafael@kernel.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