From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [PATCH 0/3] pinctrl: don't use gpiod_to_chip()
Date: Wed, 15 Nov 2023 17:49:58 +0100 [thread overview]
Message-ID: <20231115165001.2932350-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Let's start working towards removing gpiod_to_chip() from the kernel.
Start with pinctrl. The first patch should go through the GPIO tree
and become available through an immutable tag so that we can get more
conversions in this cycle elsewhere.
Bartosz Golaszewski (3):
gpiolib: provide gpio_devie_get_label()
pinctrl: stop using gpiod_to_chip()
pinctrl: don't include GPIOLIB private header
drivers/gpio/gpiolib.c | 14 ++++++++++++++
drivers/pinctrl/core.c | 18 ++++++++----------
include/linux/gpio/driver.h | 1 +
3 files changed, 23 insertions(+), 10 deletions(-)
--
2.40.1
next reply other threads:[~2023-11-15 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 16:49 Bartosz Golaszewski [this message]
2023-11-15 16:49 ` [PATCH 1/3] gpiolib: provide gpio_devie_get_label() Bartosz Golaszewski
2023-11-15 16:50 ` [PATCH 2/3] pinctrl: stop using gpiod_to_chip() Bartosz Golaszewski
2023-11-15 16:50 ` [PATCH 3/3] pinctrl: don't include GPIOLIB private header Bartosz Golaszewski
2023-11-17 21:09 ` Andy Shevchenko
2023-11-16 13:43 ` [PATCH 0/3] pinctrl: don't use gpiod_to_chip() Linus Walleij
2023-11-20 15:06 ` Bartosz Golaszewski
2023-11-24 10:01 ` Linus Walleij
2023-11-24 19:40 ` Bartosz Golaszewski
2023-11-24 23:29 ` 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=20231115165001.2932350-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--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).