From: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
To: michael@walle.cc, linus.walleij@linaro.org, brgl@bgdev.pl
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] gpio-regmap support for register fields and other hooks
Date: Sun, 3 Jul 2022 12:10:54 +0100 [thread overview]
Message-ID: <20220703111057.23246-1-aidanmacdonald.0x0@gmail.com> (raw)
This is a small series to expand the usefulness of gpio-regmap.
Patch 1 allows GPIO direction and level to be mapped to values in a register
field for cases where a one-bit-per-GPIO mapping is insufficient.
Patch 2 allows gpio-regmap to be used for the GPIO portion of a combined
pin control + GPIO driver by deferring some ops to the pin control subsystem.
Patch 3 allows drivers to provide a custom ->to_irq() hook for the GPIO chip
as an alternative to using an IRQ domain.
Aidan MacDonald (3):
gpio: regmap: Support registers with more than one bit per GPIO
gpio: regmap: Support combined GPIO and pin control drivers
gpio: regmap: Support a custom ->to_irq() hook
drivers/gpio/gpio-regmap.c | 110 ++++++++++++++++++++++++++----------
include/linux/gpio/regmap.h | 24 ++++++++
2 files changed, 103 insertions(+), 31 deletions(-)
--
2.35.1
next reply other threads:[~2022-07-03 11:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 11:10 Aidan MacDonald [this message]
2022-07-03 11:10 ` [PATCH 1/3] gpio: regmap: Support registers with more than one bit per GPIO Aidan MacDonald
2022-07-03 14:09 ` Andy Shevchenko
2022-07-04 16:03 ` Aidan MacDonald
2022-07-04 12:28 ` Michael Walle
2022-07-04 16:01 ` Aidan MacDonald
2022-07-04 19:46 ` Michael Walle
2022-07-06 20:46 ` Aidan MacDonald
2022-07-07 7:44 ` Michael Walle
2022-07-07 14:58 ` Aidan MacDonald
2022-07-03 11:10 ` [PATCH 2/3] gpio: regmap: Support combined GPIO and pin control drivers Aidan MacDonald
2022-07-03 14:14 ` Andy Shevchenko
2022-07-04 15:31 ` Aidan MacDonald
2022-07-03 11:10 ` [PATCH 3/3] gpio: regmap: Support a custom ->to_irq() hook Aidan MacDonald
2022-07-03 14:24 ` Andy Shevchenko
2022-07-04 16:38 ` Aidan MacDonald
2022-07-04 23:05 ` Linus Walleij
2022-07-05 11:09 ` Aidan MacDonald
2022-07-06 11:45 ` Andy Shevchenko
2022-07-06 20:53 ` Aidan MacDonald
2022-07-06 12:02 ` Linus Walleij
2022-07-06 13:50 ` Aidan MacDonald
2022-07-11 11:48 ` Linus Walleij
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=20220703111057.23246-1-aidanmacdonald.0x0@gmail.com \
--to=aidanmacdonald.0x0@gmail.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
/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).