[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175216036871.755014.4346115067078586712.b4-ty@kernel.org>
Date: Thu, 10 Jul 2025 16:12:48 +0100
From: Mark Brown <broonie@...nel.org>
To: Lee Jones <lee@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linus Walleij <linus.walleij@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>, Julien Panis <jpanis@...libre.com>,
Michael Walle <mwalle@...nel.org>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org
Subject: Re: (subset) [PATCH v3 0/8] mfd: tps6594: Add TI TPS652G1 support
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
Powered by blists - more mailing lists