linux-kernel - Re: [PATCH] regulator: bd718x7: Fix the BUCK7 voltage setting on BD71837

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu,  3 Jun 2021 19:41:53 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Matti Vaittinen <matti.vaittinen@...rohmeurope.com>,
        Matti Vaittinen <mazziesaccount@...il.com>
Cc:     Mark Brown <broonie@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-power@...rohmeurope.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: bd718x7: Fix the BUCK7 voltage setting on BD71837

On Mon, 24 May 2021 12:42:04 +0300, Matti Vaittinen wrote:
> The BD71837 voltages for other regulators except the first 4 BUCKs
> should be forbidden when regulator is enabled. There may be out-of-spec
> voltage spikes if the voltage is changed when these "non DVS" bucks are
> enabled. This restriction was accidentally removed when the LDO voltage
> change was allowed for BD71847. (It was not noticed that the BD71837
> BUCK7 used same voltage setting function as LDOs).
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: bd718x7: Fix the BUCK7 voltage setting on BD71837
      commit: bc537e65b09a05923f98a31920d1ab170e648dba

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