Linux PWM subsystem development
 help / color / mirror / Atom feed
From: <Hari.PrasathGE@microchip.com>
To: <claudiu.beznea@tuxon.dev>, <thierry.reding@gmail.com>,
	<u.kleine-koenig@pengutronix.de>, <Nicolas.Ferre@microchip.com>,
	<alexandre.belloni@bootlin.com>
Cc: <linux-pwm@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pwm: atmel: add missing clk_disable_unprepare()
Date: Fri, 25 Aug 2023 03:04:07 +0000	[thread overview]
Message-ID: <2aab2c4f-cff5-f13d-e879-a5b1b00ef9c7@microchip.com> (raw)
In-Reply-To: <5663e3e6-de16-e9ba-0745-b9a40676b109@tuxon.dev>

Hello Claudiu,

On 23/08/23 10:29 am, claudiu beznea wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On 8/22/23 10:04, Hari Prasath Gujulan Elango wrote:
>> Fix the below smatch warning:
>>
>> drivers/pwm/pwm-atmel-hlcdc.c:167 atmel_hlcdc_pwm_apply() warn: 'new_clk' from clk_prepare_enable() not released on lines: 112,137,142,149.
>>
> 
> Can you add a fixes tag?
> 

yes I will add it.

>> Signed-off-by: Hari Prasath Gujulan Elango <Hari.PrasathGE@microchip.com>
>> ---
>>   drivers/pwm/pwm-atmel-hlcdc.c | 17 +++++++++++++----
>>   1 file changed, 13 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/pwm/pwm-atmel-hlcdc.c b/drivers/pwm/pwm-atmel-hlcdc.c
>> index 96a709a9d49a..ce46f6c74a14 100644
>> --- a/drivers/pwm/pwm-atmel-hlcdc.c
>> +++ b/drivers/pwm/pwm-atmel-hlcdc.c
>> @@ -108,8 +108,10 @@ static int atmel_hlcdc_pwm_apply(struct pwm_chip *c, struct pwm_device *pwm,
>>                                                 ATMEL_HLCDC_CFG(0),
>>                                                 ATMEL_HLCDC_CLKPWMSEL,
>>                                                 gencfg);
>> -                     if (ret)
>> +                     if (ret) {
>> +                             clk_disable_unprepare(new_clk);
>>                                return ret;
>> +                     }
>>                }
>>
>>                do_div(pwmcval, state->period);
>> @@ -133,20 +135,27 @@ static int atmel_hlcdc_pwm_apply(struct pwm_chip *c, struct pwm_device *pwm,
>>                                         ATMEL_HLCDC_PWMPS_MASK |
>>                                         ATMEL_HLCDC_PWMPOL,
>>                                         pwmcfg);
>> -             if (ret)
>> +             if (ret) {
>> +                     clk_disable_unprepare(new_clk);
>>                        return ret;
>> +             }
>>
>>                ret = regmap_write(hlcdc->regmap, ATMEL_HLCDC_EN,
>>                                   ATMEL_HLCDC_PWM);
>> -             if (ret)
>> +             if (ret) {
>> +                     clk_disable_unprepare(new_clk);
>>                        return ret;
>> +             }
>>
>>                ret = regmap_read_poll_timeout(hlcdc->regmap, ATMEL_HLCDC_SR,
>>                                               status,
>>                                               status & ATMEL_HLCDC_PWM,
>>                                               10, 0);
>> -             if (ret)
>> +             if (ret) {
>> +                     clk_disable_unprepare(new_clk);
> 
> Can you keep a single failure point for all these?
> 
> Also, you have to set chip->cur_clk = NULL otherwise next time your apply
> will get executed the new_clk will not be enabled.
> 

I see that new_clk is assigned to cur_clk in the if (state->enabled) 
block and clk_disable_unprepare() is invoked only in the else block for 
cur_clk and its made NULL. I will cleanup all of this at a single point 
and resend v2.

Thanks,
Hari


> Thank you,
> Claudiu Beznea
> 
>>                        return ret;
>> +             }
>> +
>>        } else {
>>                ret = regmap_write(hlcdc->regmap, ATMEL_HLCDC_DIS,
>>                                   ATMEL_HLCDC_PWM);

      reply	other threads:[~2023-08-25  3:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22  7:04 [PATCH] pwm: atmel: add missing clk_disable_unprepare() Hari Prasath Gujulan Elango
2023-08-23  4:59 ` claudiu beznea
2023-08-25  3:04   ` Hari.PrasathGE [this message]

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=2aab2c4f-cff5-f13d-e879-a5b1b00ef9c7@microchip.com \
    --to=hari.prasathge@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --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