From: Thierry Reding <thierry.reding@gmail.com>
To: Guiting Shen <aarongt.shen@gmail.com>
Cc: linux-pwm@vger.kernel.org, alexandre.belloni@bootlin.com,
linux-kernel@vger.kernel.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
claudiu.beznea@microchip.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] pwm: atmel: Enable clk when pwm already enabled in bootloader
Date: Wed, 12 Jul 2023 14:31:43 +0200 [thread overview]
Message-ID: <ZK6dL84DsQDhsFWl@orome> (raw)
In-Reply-To: <90830c22-0437-591e-cee0-67b16214bc55@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1992 bytes --]
On Wed, Jul 12, 2023 at 09:45:08AM +0800, Guiting Shen wrote:
> On Wed, Jul 12, 2023 at 04:30:17AM GMT+8, Uwe Kleine-König wrote:
> > Hello,
> >
> > On Wed, Jul 12, 2023 at 04:09:05AM +0800, Guiting Shen wrote:
> >> +static int atmel_pwm_enable_clk_if_on(struct atmel_pwm_chip *atmel_pwm)
> >> +{
> >> + unsigned int i;
> >> + int err;
> >> + u32 sr;
> >> +
> >> + sr = atmel_pwm_readl(atmel_pwm, PWM_SR);
> >> + if (!sr)
> >> + return 0;
> >> +
> >> + for (i = 0; i < atmel_pwm->chip.npwm; i++) {
> >> + if (!(sr & (1 << i)))
> >> + continue;
> >> +
> >> + err = clk_enable(atmel_pwm->clk);
> >> + if (err) {
> >> + dev_err(atmel_pwm->chip.dev,
> >> + "failed to enable clock: %pe\n", ERR_PTR(err));
> >
> > Here you leak possibly a few enables. While it's not likely that the
> > (say) third enable goes wrong, it's also not that hard to handle?!
>
> The driver used the enable_count member of struct clk_core to count the
> PWM channels(4 channels). It will enable hardware clock only when one of
> the PWM channels becomed on from all PWM channels off which maybe return
> error. And in second/third/fourth times to clk_enable(), it just
> increased the enable_count of struct clk_core which would never return
> error.
>
> It maybe confused at first time to view the code.
> Do it need to add something like that: ?
>
> for (i = 0; i < atmel_pwm->chip.npwm; i++) {
> if (!(sr & (1 << i)))
> continue;
>
> err = clk_enable(atmel_pwm->clk);
> if (err) {
> dev_err(atmel_pwm->chip.dev,
> "failed to enable clock: %pe\n", ERR_PTR(err));
>
> for (i = 0; i < cnt; i++)
> clk_disable(atmel_pwm->clk);
> return err;
> }
> cnt++;
You can also achieve this by decrementing i back to zero, that way you
avoid the additional variable and you get a more natural unwinding of
what you did before.
So something like:
while (i--)
clk_disable(atmel_pwm->clk);
should do the same thing.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-07-12 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 20:09 [PATCH v3] pwm: atmel: Enable clk when pwm already enabled in bootloader Guiting Shen
2023-07-11 20:30 ` Uwe Kleine-König
2023-07-12 1:45 ` Guiting Shen
2023-07-12 10:00 ` Uwe Kleine-König
2023-07-12 12:31 ` Thierry Reding [this message]
2023-07-12 12:47 ` Uwe Kleine-König
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=ZK6dL84DsQDhsFWl@orome \
--to=thierry.reding@gmail.com \
--cc=aarongt.shen@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--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