mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: david@lechnology.com, jm@ti.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, wbg@kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] counter: ti-eqep: Fix runtime PM imbalance in ti_eqep_probe()
Date: Thu, 17 Sep 2026 01:44:13 +0100	[thread overview]
Message-ID: <20260917014413.2f9ee87c@jic23-hlaptop> (raw)
In-Reply-To: <20260916072247.1967830-1-vulab@iscas.ac.cn>

On Wed, 16 Sep 2026 07:22:47 +0000
Wentao Liang <vulab@iscas.ac.cn> wrote:

> In ti_eqep_probe(), runtime PM is enabled and acquired via
> pm_runtime_get_sync(dev). However, if devm_clk_get_enabled() fails,
> the function returns directly without calling pm_runtime_put_sync()
> and pm_runtime_disable(), leaving the runtime PM usage count and
> enable state unbalanced.
> 
> Add the missing pm_runtime_put_sync() and pm_runtime_disable() calls
> on the clock error path.
> 
> Fixes: 0cf81c73e4c6 ("counter: ti-eqep: enable clock at probe")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
>  drivers/counter/ti-eqep.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/counter/ti-eqep.c b/drivers/counter/ti-eqep.c
> index d21c157e531a..84fbf500b0f8 100644
> --- a/drivers/counter/ti-eqep.c
> +++ b/drivers/counter/ti-eqep.c
> @@ -548,8 +548,11 @@ static int ti_eqep_probe(struct platform_device *pdev)
>  	pm_runtime_get_sync(dev);
>  
>  	clk = devm_clk_get_enabled(dev, NULL);
> -	if (IS_ERR(clk))
> +	if (IS_ERR(clk)) {
> +		pm_runtime_put_sync(dev);
> +		pm_runtime_disable(dev);

Having manual cleanup immediately after a devm call is not a good sign as
it will be out of order.  Use devm_pm_runtime_enable() and consider if the
pm_runtime_get_sync() that the put is reversing is actually needed.
I suspect not.

>  		return dev_err_probe(dev, PTR_ERR(clk), "failed to enable clock\n");
> +	}
>  
>  	err = counter_add(counter);
>  	if (err < 0) {


      reply	other threads:[~2026-09-17  0:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16  7:22 Wentao Liang
2026-09-17  0:44 ` Jonathan Cameron [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=20260917014413.2f9ee87c@jic23-hlaptop \
    --to=jic23@kernel.org \
    --cc=david@lechnology.com \
    --cc=jm@ti.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vulab@iscas.ac.cn \
    --cc=wbg@kernel.org \
    /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

all inboxes | Powered by JetHome®