From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Viresh Kumar <vireshk@kernel.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@ew.tq-group.com, linux-arm-kernel@lists.infradead.org,
virtualization@lists.linux.dev,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [PATCH 00/12] gpio: use new GPIO line value setter callbacks
Date: Mon, 07 Jul 2025 09:50:13 +0200 [thread overview]
Message-ID: <20250707-gpiochip-set-rv-gpio-round4-v1-0-35668aaaf6d2@linaro.org> (raw)
Commit 98ce1eb1fd87e ("gpiolib: introduce gpio_chip setters that return
values") added new line setter callbacks to struct gpio_chip. They allow
to indicate failures to callers. We're in the process of converting all
GPIO controllers to using them before removing the old ones. This series
converts another round of GPIO drivers.
To:
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
---
Bartosz Golaszewski (12):
gpio: tps65910: use new GPIO line value setter callbacks
gpio: tps65912: check the return value of regmap_update_bits()
gpio: tps65912: use new GPIO line value setter callbacks
gpio: tps68470: use new GPIO line value setter callbacks
gpio: tqmx86: use new GPIO line value setter callbacks
gpio: ts4900: use new GPIO line value setter callbacks
gpio: twl4030: use new GPIO line value setter callbacks
gpio: twl6040: use new GPIO line value setter callbacks
gpio: twl6040: set line value in .direction_out()
gpio: uniphier: use new GPIO line value setter callbacks
gpio: viperboard: use new GPIO line value setter callbacks
gpio: virtio: use new GPIO line value setter callbacks
drivers/gpio/gpio-tps65910.c | 21 ++++----
drivers/gpio/gpio-tps65912.c | 17 +++---
drivers/gpio/gpio-tps68470.c | 14 +++--
drivers/gpio/gpio-tqmx86.c | 8 +--
drivers/gpio/gpio-ts4900.c | 14 ++---
drivers/gpio/gpio-twl4030.c | 23 ++++----
drivers/gpio/gpio-twl6040.c | 23 ++++----
drivers/gpio/gpio-uniphier.c | 16 +++---
drivers/gpio/gpio-viperboard.c | 116 ++++++++++++++++++++++-------------------
drivers/gpio/gpio-virtio.c | 7 +--
10 files changed, 144 insertions(+), 115 deletions(-)
---
base-commit: 26ffb3d6f02cd0935fb9fa3db897767beee1cb2a
change-id: 20250703-gpiochip-set-rv-gpio-round4-e3b568fda584
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
next reply other threads:[~2025-07-07 7:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 7:50 Bartosz Golaszewski [this message]
2025-07-07 7:50 ` [PATCH 01/12] gpio: tps65910: use new GPIO line value setter callbacks Bartosz Golaszewski
2025-07-07 7:50 ` [PATCH 02/12] gpio: tps65912: check the return value of regmap_update_bits() Bartosz Golaszewski
2025-07-07 7:50 ` [PATCH 03/12] gpio: tps65912: use new GPIO line value setter callbacks Bartosz Golaszewski
2025-07-07 7:50 ` [PATCH 04/12] gpio: tps68470: " Bartosz Golaszewski
2025-07-07 7:50 ` [PATCH 05/12] gpio: tqmx86: " Bartosz Golaszewski
2025-07-07 12:32 ` Matthias Schiffer
2025-07-07 7:50 ` [PATCH 06/12] gpio: ts4900: " Bartosz Golaszewski
2025-07-07 7:50 ` [PATCH 07/12] gpio: twl4030: " Bartosz Golaszewski
2025-07-07 7:50 ` [PATCH 08/12] gpio: twl6040: " Bartosz Golaszewski
2025-07-07 7:50 ` [PATCH 09/12] gpio: twl6040: set line value in .direction_out() Bartosz Golaszewski
2025-07-07 7:50 ` [PATCH 10/12] gpio: uniphier: use new GPIO line value setter callbacks Bartosz Golaszewski
2025-07-08 0:30 ` Kunihiko Hayashi
2025-07-07 7:50 ` [PATCH 11/12] gpio: viperboard: " Bartosz Golaszewski
2025-07-07 7:50 ` [PATCH 12/12] gpio: virtio: " Bartosz Golaszewski
2025-07-07 8:29 ` Viresh Kumar
2025-07-13 8:45 ` [PATCH 00/12] gpio: " Bartosz Golaszewski
-- strict thread matches above, loose matches on Subject: below --
2025-07-02 9:14 Bartosz Golaszewski
2025-07-07 7:46 ` Bartosz Golaszewski
2025-06-25 10:33 Bartosz Golaszewski
2025-07-02 9:10 ` Bartosz Golaszewski
2025-06-17 12:24 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=20250707-gpiochip-set-rv-gpio-round4-v1-0-35668aaaf6d2@linaro.org \
--to=brgl@bgdev.pl \
--cc=bartosz.golaszewski@linaro.org \
--cc=hayashi.kunihiko@socionext.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@ew.tq-group.com \
--cc=mhiramat@kernel.org \
--cc=vireshk@kernel.org \
--cc=virtualization@lists.linux.dev \
/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).