All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Gong <b38343@freescale.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: pfuze100: Use regulator_map_voltage_ascend
Date: Mon, 29 Jul 2013 17:35:21 +0800	[thread overview]
Message-ID: <20130729093519.GB319@Robin-OptiPlex-780> (raw)
In-Reply-To: <1375083538.7272.4.camel@phoenix>

Yes, it's reasonable from performance view.
On Mon, Jul 29, 2013 at 03:38:58PM +0800, Axel Lin wrote:
> All table based voltage list have ascendant order.
> Use regulator_map_voltage_ascend for them.
> 
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
>  drivers/regulator/pfuze100-regulator.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/regulator/pfuze100-regulator.c b/drivers/regulator/pfuze100-regulator.c
> index e9e8ae3..dbb6e1a 100644
> --- a/drivers/regulator/pfuze100-regulator.c
> +++ b/drivers/regulator/pfuze100-regulator.c
> @@ -144,6 +144,7 @@ static struct regulator_ops pfuze100_sw_regulator_ops = {
>  
>  static struct regulator_ops pfuze100_swb_regulator_ops = {
>  	.list_voltage = regulator_list_voltage_table,
> +	.map_voltage = regulator_map_voltage_ascend,
>  	.set_voltage_sel = regulator_set_voltage_sel_regmap,
>  	.get_voltage_sel = regulator_get_voltage_sel_regmap,
>  
> -- 
> 1.8.1.2
> 
> 
> 
> 


  reply	other threads:[~2013-07-29  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  7:38 [PATCH] regulator: pfuze100: Use regulator_map_voltage_ascend Axel Lin
2013-07-29  9:35 ` Robin Gong [this message]
2013-07-29 11:43 ` 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=20130729093519.GB319@Robin-OptiPlex-780 \
    --to=b38343@freescale.com \
    --cc=axel.lin@ingics.com \
    --cc=broonie@kernel.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 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.