All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: cy_huang <u0084500@gmail.com>
Cc: broonie@kernel.org, linux-kernel@vger.kernel.org,
	lgirdwood@gmail.com, axel.lin@ingics.com, cy_huang@richtek.com
Subject: Re: [PATCH v2] regulator: rt5033: Use linear ranges to map all voltage selection
Date: Tue, 6 Jul 2021 09:24:13 +0100	[thread overview]
Message-ID: <YOQTLWsXpTOK58dr@dell> (raw)
In-Reply-To: <1625553939-9109-1-git-send-email-u0084500@gmail.com>

On Tue, 06 Jul 2021, cy_huang wrote:

> From: ChiYuan Huang <cy_huang@richtek.com>
> 
> Instead of linear mapping, Use linear range to map all voltage selection.
> 
> Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
> ---
> Since v2
> - recover the volt number back in rt5033-private.h
> - Add the n_voltages from v1 back.
> 
> Even though commit 6549c46af855 ("regulator: rt5033: Fix n_voltages settings for BUCK and LDO")
> can fix the linear mapping to the correct min/max voltage
> But there're still non-step ranges for the reserved value.
> 
> To use the linear range can fix it for mapping all voltage selection.
> ---
>  drivers/regulator/rt5033-regulator.c | 21 +++++++++++++++------

>  include/linux/mfd/rt5033-private.h   |  4 ++--

Acked-by: Lee Jones <lee.jones@linaro.org>

>  2 files changed, 17 insertions(+), 8 deletions(-)

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2021-07-06  8:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06  6:45 [PATCH v2] regulator: rt5033: Use linear ranges to map all voltage selection cy_huang
2021-07-06  6:49 ` Axel Lin
2021-07-06  8:24 ` Lee Jones [this message]
2021-07-12 10:45 ` Mark Brown

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=YOQTLWsXpTOK58dr@dell \
    --to=lee.jones@linaro.org \
    --cc=axel.lin@ingics.com \
    --cc=broonie@kernel.org \
    --cc=cy_huang@richtek.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=u0084500@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.