From: Heiner Kallweit <hkallweit1@gmail.com>
To: Dmitry Rokosov <ddrokosov@sberdevices.ru>
Cc: "Jerome Brunet" <jbrunet@baylibre.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Neil Armstrong" <narmstrong@baylibre.com>,
"Kevin Hilman" <khilman@baylibre.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
linux-pwm@vger.kernel.org, kernel@sberdevices.ru
Subject: Re: [PATCH] pwm: meson: simplify calculation in meson_pwm_get_state
Date: Fri, 21 Apr 2023 17:33:29 +0200 [thread overview]
Message-ID: <5b1a84ee-1f96-1585-5167-4f4e266a7fb7@gmail.com> (raw)
In-Reply-To: <20230421145723.oq7zqbhhz4fhkmyj@CAB-WSD-L081021>
On 21.04.2023 16:57, Dmitry Rokosov wrote:
> Hello Heiner,
>
> Thank you for the patch! Please find my comments below.
>
> On Wed, Apr 19, 2023 at 11:30:55PM +0200, Heiner Kallweit wrote:
>> I don't see a reason why we should treat the case lo < hi that
>> different and return 0 as period and duty_cycle. Let's handle it as
>> normal use case and also remove the optimization for lo == 0.
>> I think the improved readability is worth it.
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>
> Inside this patch, in my opinion, you have not only simplified and
> optimized but have also modified the logic. It is important to provide
> more details on this modification. Previously, in cases where
> (channel->lo != 0) && (channel->lo < channel->hi), period and duty_cycle
> were not calculated. However, in your patchset, duty_cycle and polarity
> are calculated and returned to the caller in such cases.
> Can you please share the details of why this is the right solution?
It's the obvious solution. I see no reason to return all zero's for
lo < hi, and also the commit that added this calculation doesn't provide
an explanation. It just references the calculation in meson_pwm_calc(),
however I fail to see that lo < hi is treated differently there.
c375bcbaabdb ("pwm: meson: Read the full hardware state in meson_pwm_get_state()")
> Also, please rephrase the commit message using 'modify' instead of
> 'simplify'.
>
>> ---
>> drivers/pwm/pwm-meson.c | 14 ++------------
>> 1 file changed, 2 insertions(+), 12 deletions(-)
>>
>> diff --git a/drivers/pwm/pwm-meson.c b/drivers/pwm/pwm-meson.c
>> index 5732300eb..3865538dd 100644
>> --- a/drivers/pwm/pwm-meson.c
>> +++ b/drivers/pwm/pwm-meson.c
>> @@ -351,18 +351,8 @@ static int meson_pwm_get_state(struct pwm_chip *chip, struct pwm_device *pwm,
>> channel->lo = FIELD_GET(PWM_LOW_MASK, value);
>> channel->hi = FIELD_GET(PWM_HIGH_MASK, value);
>>
>> - if (channel->lo == 0) {
>> - state->period = meson_pwm_cnt_to_ns(chip, pwm, channel->hi);
>> - state->duty_cycle = state->period;
>> - } else if (channel->lo >= channel->hi) {
>> - state->period = meson_pwm_cnt_to_ns(chip, pwm,
>> - channel->lo + channel->hi);
>> - state->duty_cycle = meson_pwm_cnt_to_ns(chip, pwm,
>> - channel->hi);
>> - } else {
>> - state->period = 0;
>> - state->duty_cycle = 0;
>> - }
>> + state->period = meson_pwm_cnt_to_ns(chip, pwm, channel->lo + channel->hi);
>> + state->duty_cycle = meson_pwm_cnt_to_ns(chip, pwm, channel->hi);
>>
>> state->polarity = PWM_POLARITY_NORMAL;
>>
>> --
>> 2.40.0
>>
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-04-21 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 21:30 [PATCH] pwm: meson: simplify calculation in meson_pwm_get_state Heiner Kallweit
2023-04-21 14:57 ` Dmitry Rokosov
2023-04-21 15:33 ` Heiner Kallweit [this message]
2023-04-21 19:14 ` Dmitry Rokosov
2023-04-23 17:59 ` Martin Blumenstingl
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=5b1a84ee-1f96-1585-5167-4f4e266a7fb7@gmail.com \
--to=hkallweit1@gmail.com \
--cc=ddrokosov@sberdevices.ru \
--cc=jbrunet@baylibre.com \
--cc=kernel@sberdevices.ru \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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