From: Jose Javier Rodriguez Barbarin <dev-josejavier.rodriguez@duagon.com>
To: linusw@kernel.org, brgl@kernel.org, wbg@kernel.org
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Jose Javier Rodriguez Barbarin
<dev-josejavier.rodriguez@duagon.com>
Subject: [RFC PATCH v2 0/3] gpio: add PMIO support to gpio-mmio
Date: Mon, 13 Apr 2026 12:23:23 +0200 [thread overview]
Message-ID: <20260413102326.59343-1-dev-josejavier.rodriguez@duagon.com> (raw)
This series is an RFC for adding port-mapped I/O (PMIO) support to
gpio-mmio.
This v2 comes with all suggestions done by Linux Walleij in the
initial review [1].
For keeping compatibility with gpio_generic_chip, a new _config struct
was added instead of extending gpio_generic_chip_config. Using such new
_config struct, called gpio_generic_chip_port_config, requires a new API
function gpio_generic_chip_port_init() to access to that new structure.
Besides, structure gpio_chip_reg has been transformed to union. It reflects
better that MMIO and PMIO chips will only use one of them, saving memory
as well.
I'm still sending this as RFC but I don't know if I should send this as a
regular PATCH series.
[1] https://lore.kernel.org/linux-gpio/20260407184805.807328-1-dev-josejavier.rodriguez@duagon.com
---
Changes in v2:
- Move struct gpio_chip_reg to union gpio_chip_reg.
- Add a new gpio-mmio API function to init PMIO generic chips.
Jose Javier Rodriguez Barbarin (3):
gpio: mmio: convert accessors to generic register descriptors
gpio: mmio: add port-mapped read/write callbacks
gpio: mmio: add port-mapped support for gpio_generic_chip
drivers/gpio/gpio-mmio.c | 330 ++++++++++++++++++++++++-----------
include/linux/gpio/generic.h | 78 ++++++++-
2 files changed, 300 insertions(+), 108 deletions(-)
--
2.53.0
next reply other threads:[~2026-04-13 10:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 10:23 Jose Javier Rodriguez Barbarin [this message]
2026-04-13 10:23 ` [RFC PATCH v2 1/3] gpio: mmio: convert accessors to generic register descriptors Jose Javier Rodriguez Barbarin
2026-04-22 16:41 ` Linus Walleij
2026-04-13 10:23 ` [RFC PATCH v2 2/3] gpio: mmio: add port-mapped read/write callbacks Jose Javier Rodriguez Barbarin
2026-04-22 16:42 ` Linus Walleij
2026-04-13 10:23 ` [RFC PATCH v2 3/3] gpio: mmio: add port-mapped support for gpio_generic_chip Jose Javier Rodriguez Barbarin
2026-04-22 16:43 ` Linus Walleij
2026-04-22 16:44 ` [RFC PATCH v2 0/3] gpio: add PMIO support to gpio-mmio Linus Walleij
2026-04-23 8:00 ` Bartosz Golaszewski
2026-04-23 15:14 ` Jose Javier Rodriguez Barbarin
2026-04-23 16:26 ` Bartosz Golaszewski
2026-04-28 9:56 ` 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=20260413102326.59343-1-dev-josejavier.rodriguez@duagon.com \
--to=dev-josejavier.rodriguez@duagon.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wbg@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
all inboxes | Powered by JetHome®