linux-kernel - Re: [PATCH v2] regulator: TPS6287X: Use min/max uV to get VRANGE

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]

Message-Id: <173755188009.28873.342950627100571333.b4-ty@kernel.org>
Date: Wed, 22 Jan 2025 13:18:00 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Jonas Andreasson <jonas.andreasson@...s.com>
Cc: linux-kernel@...r.kernel.org, kernel@...s.com
Subject: Re: [PATCH v2] regulator: TPS6287X: Use min/max uV to get VRANGE

On Tue, 21 Jan 2025 15:37:50 +0100, Jonas Andreasson wrote:
> Changing voltage might ignore slew rate and cause a current surge.
> 
> With current implementation the driver will get the regulator to change
> the voltage range used during run time. According to communication I
> have had with Texas Instruments, this is not intended, since the
> Dynamic Voltage Scaling in the hardware is only designed to work
> within a voltage range. The current implementation will therefore
> ignore the slew rate that is defined in devicetree when the voltage
> range is changed during use.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: TPS6287X: Use min/max uV to get VRANGE
      commit: 3028583d1314a70ca273c51e0265f698c0bd5760

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