struct gpio_chip now has callbacks for setting line values that return
an integer, allowing to indicate failures. We're in the process of
converting all GPIO drivers to using the new API. This series converts
the only GPIO controller under drivers/regulator/ and - while at it -
refactors the code a bit.

Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
---
Bartosz Golaszewski (4):
      regulator: rpi-panel-attiny: don't double-check GPIO range
      regulator: rpi-panel-attiny: use devres for mutex management
      regulator: rpi-panel-attiny: use lock guards for the state mutex
      regulator: rpi-panel-attiny: use new GPIO line value setter callbacks

 drivers/regulator/rpi-panel-attiny-regulator.c | 81 +++++++++-----------------
 1 file changed, 28 insertions(+), 53 deletions(-)
---
base-commit: 0af2f6be1b4281385b618cb86ad946eded089ac8
change-id: 20250331-gpiochip-set-rv-regulator-e12b909f5af7

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

On Tue, 08 Apr 2025 09:36:27 +0200, Bartosz Golaszewski wrote:
> struct gpio_chip now has callbacks for setting line values that return
> an integer, allowing to indicate failures. We're in the process of
> converting all GPIO drivers to using the new API. This series converts
> the only GPIO controller under drivers/regulator/ and - while at it -
> refactors the code a bit.
> 
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/4] regulator: rpi-panel-attiny: don't double-check GPIO range
      commit: 06bab1f101337ae9469a7d2c6ac4de5db64e8160
[2/4] regulator: rpi-panel-attiny: use devres for mutex management
      commit: 1326e295d6b4ffc9647bd4f073b787b4f79d6b6e
[3/4] regulator: rpi-panel-attiny: use lock guards for the state mutex
      commit: 50faedda12e46918a11194a30c2bedf2b983fae2
[4/4] regulator: rpi-panel-attiny: use new GPIO line value setter callbacks
      commit: 936df52c29b0d422665c5e84b0cffae61611411b

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark