From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: Mark Brown <broonie@kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
Liam Girdwood <lgirdwood@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFT] regulator: max8972: Fix setting ramp delay
Date: Mon, 30 May 2016 11:04:26 +0200 [thread overview]
Message-ID: <574C021A.2080502@samsung.com> (raw)
In-Reply-To: <CAFRkauBY=B_CLQnmEY5AJ-J63HiKyYqA9Jd8AipwrVk7vfpXmA@mail.gmail.com>
On 05/30/2016 10:52 AM, Axel Lin wrote:
> 2016-05-30 16:48 GMT+08:00 Krzysztof Kozlowski <k.kozlowski@samsung.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.
>
> Assume rdev->constraints->ramp_delay is 20000.
>
> Original code will set MAX8973_RAMP_12mV_PER_US.
>
> However, in regulator_set_voltage_time_sel()
> return DIV_ROUND_UP(abs(new_volt - old_volt), ramp_delay);
>
> This return value is not enough if the device is using MAX8973_RAMP_12mV_PER_US
> setting.
Thanks, now it makes sense but the commit message needs improvements.
The problem is that current code for .set_ramp_delay() rounds down the
value written to register, while the implementation of
.set_voltage_time_sel() works on original constraints (not rounded down).
Please, fix the message.
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-05-30 9:04 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
2016-05-30 8:52 ` Axel Lin
2016-05-30 9:04 ` Krzysztof Kozlowski [this message]
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=574C021A.2080502@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 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.