From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Axel Lin <axel.lin@ingics.com>, Mark Brown <broonie@kernel.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFT] regulator: max8972: Fix setting ramp delay
Date: Mon, 30 May 2016 10:48:28 +0200 [thread overview]
Message-ID: <574BFE5C.5010006@samsung.com> (raw)
In-Reply-To: <1464520619.14023.4.camel@ingics.com>
On 05/29/2016 01:16 PM, Axel Lin wrote:
> Current code can set ramp delay to a wrong setting that the return value
> from .set_voltage_time_sel is not enough for proper delay.
I don't understand what yo wanted to say here. What wrong setting is
possible? Why do you mention set_voltage_time_sel() here?
Can you elaborate?
The only difference I spotted is how you round up the ramp_delay values.
Best regards,
Krzysztof
> Fix the logic in .set_ramp_delay and also remove unused ret_val variable.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> drivers/regulator/max8973-regulator.c | 16 ++++++----------
> 1 file changed, 6 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/regulator/max8973-regulator.c b/drivers/regulator/max8973-regulator.c
> index 08d2f13..3958f50 100644
> --- a/drivers/regulator/max8973-regulator.c
> +++ b/drivers/regulator/max8973-regulator.c
> @@ -271,22 +271,18 @@ static int max8973_set_ramp_delay(struct regulator_dev *rdev,
> struct max8973_chip *max = rdev_get_drvdata(rdev);
> unsigned int control;
> int ret;
> - int ret_val;
>
> /* Set ramp delay */
> - if (ramp_delay < 25000) {
> + if (ramp_delay <= 12000)
> control = MAX8973_RAMP_12mV_PER_US;
> - ret_val = 12000;
> - } else if (ramp_delay < 50000) {
> + else if (ramp_delay <= 25000)
> control = MAX8973_RAMP_25mV_PER_US;
> - ret_val = 25000;
> - } else if (ramp_delay < 200000) {
> + else if (ramp_delay <= 50000)
> control = MAX8973_RAMP_50mV_PER_US;
> - ret_val = 50000;
> - } else {
> + else if (ramp_delay <= 200000)
> control = MAX8973_RAMP_200mV_PER_US;
> - ret_val = 200000;
> - }
> + else
> + return -EINVAL;
>
> ret = regmap_update_bits(max->regmap, MAX8973_CONTROL1,
> MAX8973_RAMP_MASK, control);
>
next prev parent reply other threads:[~2016-05-30 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 11:16 [PATCH RFT] regulator: max8972: Fix setting ramp delay Axel Lin
2016-05-30 8:48 ` Krzysztof Kozlowski [this message]
2016-05-30 8:52 ` Axel Lin
2016-05-30 9:04 ` Krzysztof Kozlowski
2016-05-30 16:01 ` Applied "regulator: max8973: Fix setting ramp delay" to the regulator tree 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=574BFE5C.5010006@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=axel.lin@ingics.com \
--cc=broonie@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mperttunen@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox