linux-kernel - Re: [PATCH v2 2/2] regulator: tps6287x: Force writing VSEL bit

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: Tue, 21 May 2024 12:18:51 +0100
From: Mark Brown <broonie@...nel.org>
To: Matti Vaittinen <mazziesaccount@...il.com>, 
 Matti Vaittinen <mazziesaccount@...il.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, 
 Mårten Lindahl <marten.lindahl@...s.com>, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] regulator: tps6287x: Force writing VSEL bit

On Mon, 20 May 2024 15:36:55 +0300, Matti Vaittinen wrote:
> The data-sheet for TPS6287x-Q1
> https://www.ti.com/lit/ds/symlink/tps62873-q1.pdf
> states at chapter 9.3.6.1 Output Voltage Range:
> 
> "Note that every change to the VRANGE[1:0] bits must be followed by a
> write to the VSET register, even if the value of the VSET[7:0] bits does
> not change."
> 
> [...]

Applied to

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

Thanks!

[2/2] regulator: tps6287x: Force writing VSEL bit
      commit: 1ace99d7c7c4c801c0660246f741ff846a9b8e3c

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