[PATCH 0/3] gpio: deprecate and track the removal of the GPIOD_FLAGS_BIT_NONEXCLUSIVE flag

Bartosz Golaszewski posted 3 patches 8 months, 3 weeks ago
MAINTAINERS                   |  1 +
drivers/gpio/TODO             | 14 ++++++++++++++
include/linux/gpio/consumer.h |  1 +
3 files changed, 16 insertions(+)
[PATCH 0/3] gpio: deprecate and track the removal of the GPIOD_FLAGS_BIT_NONEXCLUSIVE flag
Posted by Bartosz Golaszewski 8 months, 3 weeks ago
This feature is another pet-peeve of mine. It's a hack that people
started using and now it's in all kinds of drivers. It doesn't really
explain what it actually does, and it implements it badly.

Let's deprecate it officially, add it to MAINTAINERS keywords so that it
pops up on our radars when used again, add a task to track it and I plan
to use the power sequencing subsystem to handle the cases where
non-exclusive access to GPIOs is required.

Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
---
Bartosz Golaszewski (3):
      gpio: deprecate the GPIOD_FLAGS_BIT_NONEXCLUSIVE flag
      MAINTAINERS: add another keyword for the GPIO subsystem
      gpio: TODO: track the removal of GPIOD_FLAGS_BIT_NONEXCLUSIVE

 MAINTAINERS                   |  1 +
 drivers/gpio/TODO             | 14 ++++++++++++++
 include/linux/gpio/consumer.h |  1 +
 3 files changed, 16 insertions(+)
---
base-commit: 405e2241def89c88f008dcb899eb5b6d4be8b43c
change-id: 20250331-gpio-todo-remove-nonexclusive-ed875467eb56

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Re: [PATCH 0/3] gpio: deprecate and track the removal of the GPIOD_FLAGS_BIT_NONEXCLUSIVE flag
Posted by Linus Walleij 8 months, 3 weeks ago
On Mon, Mar 31, 2025 at 11:00 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:

> This feature is another pet-peeve of mine. It's a hack that people
> started using and now it's in all kinds of drivers. It doesn't really
> explain what it actually does, and it implements it badly.
>
> Let's deprecate it officially, add it to MAINTAINERS keywords so that it
> pops up on our radars when used again, add a task to track it and I plan
> to use the power sequencing subsystem to handle the cases where
> non-exclusive access to GPIOs is required.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

Some like drivers/fsi/fsi-master-aspeed.c seem to be just a bug,
are all non-regulator users bugs?

In general though:
Acked-by: Linus Walleij <linus.walleij@linaro.org>

Yours,
Linus Walleij