From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Yinbo Zhu <zhuyinbo@loongson.cn>,
Hoan Tran <hoan@os.amperecomputing.com>,
Manivannan Sadhasivam <mani@kernel.org>,
Yang Shen <shenyang39@huawei.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-unisoc@lists.infradead.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [PATCH 00/14] gpio: replace legacy bgpio_init() with its modernized alternative
Date: Tue, 12 Aug 2025 11:51:57 +0200 [thread overview]
Message-ID: <20250812-gpio-mmio-gpio-conv-v1-0-9f43e95dea98@linaro.org> (raw)
This is the first round of GPIO driver conversions to using the
modernized variant of the gpio-mmio API.
While at it: sprinkle in some additional tweaks and refactoring.
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
---
Bartosz Golaszewski (14):
gpio: generic: provide to_gpio_generic_chip()
gpio: generic: provide helpers for reading and writing registers
gpio: hisi: use the BGPIOF_UNREADABLE_REG_DIR flag
gpio: ts4800: remove the unnecessary call to platform_set_drvdata()
gpio: ts4800: use generic device properties
gpio: ts4800: use dev_err_probe()
gpio: ts4800: use new generic GPIO chip API
gpio: loongson-64bit: use new generic GPIO chip API
gpio: dwapb: use new generic GPIO chip API
gpio: amdpt: use new generic GPIO chip API
gpio: rda: use new generic GPIO chip API
gpio: grgpio: use new generic GPIO chip API
gpio: mpc8xxx: use new generic GPIO chip API
gpio: ge: use new generic GPIO chip API
drivers/gpio/gpio-amdpt.c | 44 +++++-----
drivers/gpio/gpio-dwapb.c | 160 ++++++++++++++++++++-----------------
drivers/gpio/gpio-ge.c | 25 ++++--
drivers/gpio/gpio-grgpio.c | 87 ++++++++++----------
drivers/gpio/gpio-hisi.c | 3 +-
drivers/gpio/gpio-loongson-64bit.c | 42 +++++-----
drivers/gpio/gpio-mpc8xxx.c | 102 +++++++++++++----------
drivers/gpio/gpio-rda.c | 35 ++++----
drivers/gpio/gpio-ts4800.c | 39 ++++-----
include/linux/gpio/generic.h | 37 +++++++++
10 files changed, 337 insertions(+), 237 deletions(-)
---
base-commit: 8f5ae30d69d7543eee0d70083daf4de8fe15d585
change-id: 20250728-gpio-mmio-gpio-conv-623517c3df74
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
next reply other threads:[~2025-08-12 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 9:51 Bartosz Golaszewski [this message]
2025-08-12 9:51 ` [PATCH 01/14] gpio: generic: provide to_gpio_generic_chip() Bartosz Golaszewski
2025-08-19 10:17 ` Linus Walleij
2025-08-12 9:51 ` [PATCH 02/14] gpio: generic: provide helpers for reading and writing registers Bartosz Golaszewski
2025-08-12 9:52 ` [PATCH 03/14] gpio: hisi: use the BGPIOF_UNREADABLE_REG_DIR flag Bartosz Golaszewski
2025-08-12 9:52 ` [PATCH 04/14] gpio: ts4800: remove the unnecessary call to platform_set_drvdata() Bartosz Golaszewski
2025-08-12 9:52 ` [PATCH 05/14] gpio: ts4800: use generic device properties 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=20250812-gpio-mmio-gpio-conv-v1-0-9f43e95dea98@linaro.org \
--to=brgl@bgdev.pl \
--cc=bartosz.golaszewski@linaro.org \
--cc=hoan@os.amperecomputing.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-unisoc@lists.infradead.org \
--cc=mani@kernel.org \
--cc=shenyang39@huawei.com \
--cc=zhuyinbo@loongson.cn \
/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).