linux-kernel - Re: [RFC PATCH 0/3] regulator: bd718x7: support voltage scaling

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: <160504430244.42164.13300869438079572457.b4-ty@kernel.org>
Date:   Tue, 10 Nov 2020 21:38:22 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Matti Vaittinen <matti.vaittinen@...rohmeurope.com>,
        matti.vaittinen@...il.com, mazziesaccount@...il.com
Cc:     Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org,
        Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
        linux-power@...rohmeurope.com
Subject: Re: [RFC PATCH 0/3] regulator: bd718x7: support voltage scaling

On Tue, 10 Nov 2020 10:19:16 +0200, Matti Vaittinen wrote:
> RFC for adding a support for typical voltage scaling connection
> 
> In few occasions there has been a need to scale the voltage output
> from bucks on BD71837. Usually this is done when buck8 is used to
> power specific GPU which can utilize voltages down to 0.7V. As lowest
> the buck8 on BD71837 can go is 0.8V, and external connection is used to
> scale the voltages.
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: BD71837 support commonly used feedback connection
      commit: 1e908b2419ea828dfad9819e5c01322a93665356
[2/3] regulator: BD71847 support commonly used feedback connection
      commit: b54a27d8109fc8f18cec3e0663f8e81ea727e3c6
[3/3] regulator: bd718x7: Support external connection to scale voltages
      commit: d2ad981151b3a812e961c8ee0ffd7e349b4027d6

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