[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <168131726333.91225.1829664211081647779.b4-ty@kernel.org>
Date: Wed, 12 Apr 2023 17:34:23 +0100
From: Mark Brown <broonie@...nel.org>
To: Support Opensource <support.opensource@...semi.com>,
Liam Girdwood <lgirdwood@...il.com>,
Lee Jones <lee@...nel.org>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Steve Twiss <stwiss.opensource@...semi.com>,
Benjamin Bara <bbara93@...il.com>
Cc: DLG-Adam.Thomson.Opensource@...renesas.com,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
Matti Vaittinen <mazziesaccount@...il.com>,
Benjamin Bara <benjamin.bara@...data.com>,
Matti Vaittinen <mazziesaccount@...il.com>
Subject: Re: [PATCH v3 0/3] regulator: da9063: disable unused voltage
monitors
On Wed, 05 Apr 2023 19:14:33 +0200, Benjamin Bara wrote:
> Follow-up for my initial patch regarding the disabling of unused
> voltage monitors. We use the PWR_OK functionality, which asserts GP_FB2
> if every monitored voltage is in range. This patch should provide the
> possibility to deactivate a voltage monitor from the DT if the regulator
> might be disabled during run time. For this purpose, the regulator
> notification support is used:
> https://lore.kernel.org/all/cover.1622628333.git.matti.vaittinen@fi.rohmeurope.com/
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/3] regulator: da9063: add voltage monitoring registers
commit: 13186dae182ab1a2a52a53424672f49cf3e81f9b
[2/3] regulator: da9063: implement setter for voltage monitoring
commit: b8717a80e6ee6500ae396d21aac2a00947bba993
[3/3] dt-bindings: mfd: dlg,da9063: document voltage monitoring
commit: 0271b61ba3bb06fff4726951667f46e68412b8c2
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