linux-kernel - Re: [PATCH v2 1/2] regulator: pickable ranges: don't always cache vsel

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 for Android: free password hash cracker in your pocket

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

Date: Mon, 20 May 2024 20:27:12 +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 1/2] regulator: pickable ranges: don't always cache
 vsel

On Mon, 20 May 2024 15:31:33 +0300, Matti Vaittinen wrote:
> Some PMICs treat the vsel_reg same as apply-bit. Eg, when voltage range
> is changed, the new voltage setting is not taking effect until the vsel
> register is written.
> 
> Add a flag 'range_applied_by_vsel' to the regulator desc to indicate this
> behaviour and to force the vsel value to be written to hardware if range
> was changed, even if the old selector was same as the new one.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: pickable ranges: don't always cache vsel
      commit: f4f4276f985a5aac7b310a4ed040b47e275e7591

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