Add support for the TI TPS652G1 PMIC which is a stripped down
version of the TPS65224. Support for the latter has already been
merged. Refactor the regulator driver to ease adding new devices.
After doing that adding the TPS652G1 variant is really straight
forward. Some care has to be taken by the interrupt handling (of the
regulator part) because there interrupts are used for voltage
monitoring which this variant doesn't have.

As there are conflicts in the regulator tree (some constify
patches) and my patches make use of them, only the first two (or
four, that's up to Lee) can go through the MFD tree. Lee, could
you please provide an immutable tag for the other trees to merge?

v3:
 - (re)add dt binding patch that I've accidentally missed in v2

v2:
 - refactor tps6594 regulator driver to make it easier to add new
   variants

Michael Walle (8):
  dt-bindings: mfd: ti,tps6594: Add TI TPS652G1 PMIC
  mfd: tps6594: Add TI TPS652G1 support
  misc: tps6594-pfsm: Add TI TPS652G1 PMIC PFSM
  pinctrl: pinctrl-tps6594: Add TPS652G1 PMIC pinctrl and GPIO
  regulator: tps6594-regulator: remove interrupt_count
  regulator: tps6594-regulator: remove hardcoded buck config
  regulator: tps6594-regulator: refactor variant descriptions
  regulator: tps6594-regulator: Add TI TPS652G1 PMIC regulators

 .../devicetree/bindings/mfd/ti,tps6594.yaml   |   1 +
 drivers/mfd/tps6594-core.c                    |  88 ++++++-
 drivers/mfd/tps6594-i2c.c                     |  10 +-
 drivers/mfd/tps6594-spi.c                     |  10 +-
 drivers/misc/tps6594-pfsm.c                   |  31 ++-
 drivers/pinctrl/pinctrl-tps6594.c             |  35 +++
 drivers/regulator/tps6594-regulator.c         | 219 +++++++++++-------
 include/linux/mfd/tps6594.h                   |   1 +
 8 files changed, 285 insertions(+), 110 deletions(-)

-- 
2.39.5

On Thu, 03 Jul 2025, Michael Walle wrote:

> Add support for the TI TPS652G1 PMIC which is a stripped down
> version of the TPS65224. Support for the latter has already been
> merged. Refactor the regulator driver to ease adding new devices.
> After doing that adding the TPS652G1 variant is really straight
> forward. Some care has to be taken by the interrupt handling (of the
> regulator part) because there interrupts are used for voltage
> monitoring which this variant doesn't have.
> 
> As there are conflicts in the regulator tree (some constify
> patches) and my patches make use of them, only the first two (or
> four, that's up to Lee) can go through the MFD tree. Lee, could
> you please provide an immutable tag for the other trees to merge?
> 
> v3:
>  - (re)add dt binding patch that I've accidentally missed in v2

Ah, that explains it!

-- 
Lee Jones [李琼斯]

On Thu, 03 Jul 2025 13:31:45 +0200, Michael Walle wrote:
> Add support for the TI TPS652G1 PMIC which is a stripped down
> version of the TPS65224. Support for the latter has already been
> merged. Refactor the regulator driver to ease adding new devices.
> After doing that adding the TPS652G1 variant is really straight
> forward. Some care has to be taken by the interrupt handling (of the
> regulator part) because there interrupts are used for voltage
> monitoring which this variant doesn't have.
> 
> [...]

Applied to

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

Thanks!

[5/8] regulator: tps6594-regulator: remove interrupt_count
      commit: 16d1a9bf36ef649b1fdb866985b4b87584491fac
[6/8] regulator: tps6594-regulator: remove hardcoded buck config
      commit: 180a135eafa9e05657559bb04cc9eb6a86ca45f3
[7/8] regulator: tps6594-regulator: refactor variant descriptions
      commit: e64ee27abfe1e9baea14b31c0a6b6bf93ac8652c
[8/8] regulator: tps6594-regulator: Add TI TPS652G1 PMIC regulators
      commit: b30d390812c8559c5835f8ae5f490b38488fafc8

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