From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 00/11] gpiolib: add support for OF GPIO configuration binding
Date: Fri, 9 Aug 2024 16:23:54 +0200 [thread overview]
Message-ID: <20240809142405.315244-1-a.fatoum@pengutronix.de> (raw)
So far, GPIO bias configuration was done exclusively by pinctrl drivers.
All barebox pinctrl drivers work by consuming a device tree node with
a binding that differs from driver to driver and then applying the
configuration described within.
Neither GPIO or pinctrl node have any insight on what in particular is
being configured.
This is problematic when wanting to support following device tree
binding, which is so far being ignored:
gpios = <&gpioe 7 (GPIO_ACTIVE_LOW | GPIO_PULL_DOWN)>;
This series enables support for this binding for gpio-keys on STM32
platforms. More support will follow in future when providers are
extended to support the gpio_ops::set_config operation and consumers are
switched to use the GPIO descriptor API.
Ahmad Fatoum (11):
gpio: make gpio.h header self-contained
gpiolib: permit GPIO drivers to implement struct gpio_ops::set_config
pinctrl: stm32: implement generic struct gpio_ops::set_config
gpiolib: turn request/active_low into bit flags
gpiolib: don't use GPIO number API in of_hog_gpio
gpiolib: store all OF flags into GPIO descriptor
gpiolib: add support for OF GPIO configuration binding
gpiolib: use dev_gpiod_get_index device node argument throughout
gpiolib: export function to get struct gpio_desc from index
input: gpio_keys: switch to GPIO descriptor API
input: gpio-keys: request with label in DT if available
drivers/gpio/Kconfig | 14 ++
drivers/gpio/gpiolib.c | 254 +++++++++++++++++++++++++-------
drivers/input/Kconfig | 2 +-
drivers/input/gpio_keys.c | 69 +++++----
drivers/of/Kconfig | 15 ++
drivers/pinctrl/Kconfig | 1 +
drivers/pinctrl/pinctrl-stm32.c | 41 ++++++
include/gpio.h | 4 +
include/linux/gpio/consumer.h | 19 +++
include/of_gpio.h | 6 +
10 files changed, 337 insertions(+), 88 deletions(-)
--
2.39.2
next reply other threads:[~2024-08-09 14:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 14:23 Ahmad Fatoum [this message]
2024-08-09 14:23 ` [PATCH 01/11] gpio: make gpio.h header self-contained Ahmad Fatoum
2024-08-09 14:23 ` [PATCH 02/11] gpiolib: permit GPIO drivers to implement struct gpio_ops::set_config Ahmad Fatoum
2024-08-09 14:23 ` [PATCH 03/11] pinctrl: stm32: implement generic " Ahmad Fatoum
2024-08-09 14:23 ` [PATCH 04/11] gpiolib: turn request/active_low into bit flags Ahmad Fatoum
2024-08-09 14:23 ` [PATCH 05/11] gpiolib: don't use GPIO number API in of_hog_gpio Ahmad Fatoum
2024-08-09 14:24 ` [PATCH 06/11] gpiolib: store all OF flags into GPIO descriptor Ahmad Fatoum
2024-08-09 14:24 ` [PATCH 07/11] gpiolib: add support for OF GPIO configuration binding Ahmad Fatoum
2024-08-09 14:24 ` [PATCH 08/11] gpiolib: use dev_gpiod_get_index device node argument throughout Ahmad Fatoum
2024-08-09 14:24 ` [PATCH 09/11] gpiolib: export function to get struct gpio_desc from index Ahmad Fatoum
2024-08-09 14:24 ` [PATCH 10/11] input: gpio_keys: switch to GPIO descriptor API Ahmad Fatoum
2024-08-09 14:24 ` [PATCH 11/11] input: gpio-keys: request with label in DT if available Ahmad Fatoum
2024-08-14 11:00 ` [PATCH 00/11] gpiolib: add support for OF GPIO configuration binding Sascha Hauer
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=20240809142405.315244-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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