linux-kernel - Re: [PATCH] regulator: rt5033: Fix n_voltages settings for BUCK and LDO

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: <162489955393.5196.4842441856639308115.b4-ty@kernel.org>
Date:   Mon, 28 Jun 2021 18:01:58 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Lee Jones <lee.jones@...aro.org>, Axel Lin <axel.lin@...ics.com>
Cc:     Mark Brown <broonie@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        Chanwoo Choi <cw00.choi@...sung.com>,
        linux-kernel@...r.kernel.org, ChiYuan Huang <cy_huang@...htek.com>,
        Beomho Seo <beomho.seo@...sung.com>
Subject: Re: [PATCH] regulator: rt5033: Fix n_voltages settings for BUCK and LDO

On Sun, 27 Jun 2021 16:04:18 +0800, Axel Lin wrote:
> For linear regulators, the n_voltages should be (max - min) / step + 1.
> 
> Buck voltage from 1v to 3V, per step 100mV, and vout mask is 0x1f.
> If value is from 20 to 31, the voltage will all be fixed to 3V.
> And LDO also, just vout range is different from 1.2v to 3v, step is the
> same. If value is from 18 to 31, the voltage will also be fixed to 3v.

Applied to

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

Thanks!

[1/1] regulator: rt5033: Fix n_voltages settings for BUCK and LDO
      commit: 6549c46af8551b346bcc0b9043f93848319acd5c

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