From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [PATCH v1 0/2] gpiolib: legacy: Allow *gpio_request_one() to die independently
Date: Wed, 12 Nov 2025 10:32:00 +0100 [thread overview]
Message-ID: <20251112093608.1481030-1-andriy.shevchenko@linux.intel.com> (raw)
Allow *gpio_request_one() to die independently and make sure
the gpio_request_one() gone first (before gpio_request() removal).
Currently the devm_gpio_request_one() depends on gpio_request_one().
Open code the latter in the former to break the dependency. Also
convert the latter to use legacy APIs, so we can kill it first
as it's not only the logical move, but an easier task due to less
amount of the leftover users in the kernel.
Besides that, we gain a few LoCs with this small refactoring, which
I consider a positive change alone.
Andy Shevchenko (2):
gpiolib: legacy: Make sure we kill gpio_request_one() first
gpiolib: legacy: Allow to kill devm_gpio_request_one() independently
drivers/gpio/gpiolib-legacy.c | 44 +++++++++++++----------------------
1 file changed, 16 insertions(+), 28 deletions(-)
--
2.50.1
next reply other threads:[~2025-11-12 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 9:32 Andy Shevchenko [this message]
2025-11-12 9:32 ` [PATCH v1 1/2] gpiolib: legacy: Make sure we kill gpio_request_one() first Andy Shevchenko
2025-11-12 9:32 ` [PATCH v1 2/2] gpiolib: legacy: Allow to kill devm_gpio_request_one() independently Andy Shevchenko
2025-11-17 9:57 ` [PATCH v1 0/2] gpiolib: legacy: Allow *gpio_request_one() to die independently 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=20251112093608.1481030-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).