From: Mark Brown <broonie@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v2 0/4] gpio: deprecate and track the removal of GPIO workarounds for regulators
Date: Tue, 1 Apr 2025 14:27:09 +0100 [thread overview]
Message-ID: <c8ca3c8a-3201-4dde-9050-69bc2c9152c4@sirena.org.uk> (raw)
In-Reply-To: <20250401-gpio-todo-remove-nonexclusive-v2-0-7c1380797b0d@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
On Tue, Apr 01, 2025 at 02:46:41PM +0200, Bartosz Golaszewski wrote:
> Let's deprecate both symbols officially, add them to the 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.
What exactly is the plan here? The regulator (and reset) usage seems
like a reasonable one TBH - the real problem is having an API from the
GPIO subsystem to discover sharing, at the minute you can't resolve a
binding enough to find out if there's sharing without actually
requesting the GPIO.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-04-01 13:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 12:46 Bartosz Golaszewski
2025-04-01 12:46 ` [PATCH v2 1/4] gpio: deprecate the GPIOD_FLAGS_BIT_NONEXCLUSIVE flag Bartosz Golaszewski
2025-04-01 12:46 ` [PATCH v2 2/4] gpio: deprecate devm_gpiod_unhinge() Bartosz Golaszewski
2025-04-15 7:55 ` Linus Walleij
2025-04-01 12:46 ` [PATCH v2 3/4] MAINTAINERS: add more keywords for the GPIO subsystem entry Bartosz Golaszewski
2025-04-01 12:46 ` [PATCH v2 4/4] gpio: TODO: track the removal of regulator-related workarounds Bartosz Golaszewski
2025-04-01 13:27 ` Mark Brown [this message]
2025-04-01 14:42 ` [PATCH v2 0/4] gpio: deprecate and track the removal of GPIO workarounds for regulators Bartosz Golaszewski
2025-04-01 16:00 ` Mark Brown
2025-04-01 18:57 ` Bartosz Golaszewski
2025-04-01 21:55 ` Mark Brown
2025-04-02 10:05 ` Bartosz Golaszewski
2025-04-02 14:08 ` Mark Brown
2025-04-07 13:15 ` Bartosz Golaszewski
2025-04-07 13:24 ` Mark Brown
2025-04-07 13:29 ` Bartosz Golaszewski
2025-04-07 13:33 ` Mark Brown
2025-04-07 13:52 ` Mark Brown
2025-04-15 21:32 ` Linus Walleij
2025-04-17 18:57 ` Bartosz Golaszewski
2025-04-22 12:04 ` Linus Walleij
2025-04-23 12:20 ` Bartosz Golaszewski
2025-04-08 8:43 ` 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=c8ca3c8a-3201-4dde-9050-69bc2c9152c4@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--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
all inboxes | Powered by JetHome®