mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Lee Jones <lee.jones@linaro.org>, Axel Lin <axel.lin@ingics.com>
Cc: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	linux-kernel@vger.kernel.org,
	ChiYuan Huang <cy_huang@richtek.com>,
	Beomho Seo <beomho.seo@samsung.com>
Subject: Re: [PATCH] regulator: rt5033: Fix n_voltages settings for BUCK and LDO
Date: Mon, 28 Jun 2021 18:01:58 +0100	[thread overview]
Message-ID: <162489955393.5196.4842441856639308115.b4-ty@kernel.org> (raw)
In-Reply-To: <20210627080418.1718127-1-axel.lin@ingics.com>

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

      reply	other threads:[~2021-06-28 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27  8:04 Axel Lin
2021-06-28 17:01 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=162489955393.5196.4842441856639308115.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=axel.lin@ingics.com \
    --cc=beomho.seo@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=cy_huang@richtek.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®