linux-kernel - Re: [PATCH v2] regulator: pca9450: Clear PRESET

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]

Message-Id: <161464183215.31485.14810671512981409540.b4-ty@kernel.org>
Date:   Mon, 01 Mar 2021 23:37:12 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Robin Gong <yibin.gong@....com>,
        Schrempf Frieder <frieder.schrempf@...tron.de>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     linux-kernel@...r.kernel.org,
        Rikard Falkeborn <rikard.falkeborn@...il.com>,
        Axel Lin <axel.lin@...ics.com>, stable@...r.kernel.org
Subject: Re: [PATCH v2] regulator: pca9450: Clear PRESET_EN bit to fix BUCK1/2/3 voltage setting

On Mon, 22 Feb 2021 12:52:20 +0100, Schrempf Frieder wrote:
> The driver uses the DVS registers PCA9450_REG_BUCKxOUT_DVS0 to set the
> voltage for the buck regulators 1, 2 and 3. This has no effect as the
> PRESET_EN bit is set by default and therefore the preset values are used
> instead, which are set to 850 mV.
> 
> To fix this we clear the PRESET_EN bit at time of initialization.

Applied to

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

Thanks!

[1/1] regulator: pca9450: Clear PRESET_EN bit to fix BUCK1/2/3 voltage setting
      commit: 66f9f2d5d94f374605d829b9e690e8cdc9d0d05d

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