From: William Breathitt Gray <wbg@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: William Breathitt Gray <wbg@kernel.org>,
Li Youhong <dayou5941@163.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Cosmin-Gabriel Tanislav <cosmin-gabriel.tanislav.xa@renesas.com>,
Li Youhong <liyouhong@kylinos.cn>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] counter: rz-mtu3-cnt: put runtime PM ref if counter init fails
Date: Sat, 31 Oct 2026 14:21:19 -0400 [thread overview]
Message-ID: <20261031182120.3646747-1-wbg@kernel.org> (raw)
In-Reply-To: <TY3PR01MB1134606C5DE0411FDACBF0001866C2@TY3PR01MB11346.jpnprd01.prod.outlook.com>
On Sat, Oct 31, 2026 at 04:34:32PM +0000, Biju Das wrote:
> Hi William Breathitt Gray,
>
> Thanks for the feedback.
>
> > -----Original Message-----
> > From: William Breathitt Gray <wbg@kernel.org>
> > Sent: 31 October 2026 16:29
> > Subject: Re: [PATCH v2] counter: rz-mtu3-cnt: put runtime PM ref if counter init fails
> >
> > On Sat, Oct 31, 2026 at 10:28:13PM +0800, Li Youhong wrote:
> > > From: Li Youhong <liyouhong@kylinos.cn>
> > >
> > > Counter enable takes a runtime PM reference before initialization but
> > > only puts it on disable. Drop the reference if initialization fails.
> > >
> > > Fixes: 0be8907359df ("counter: Add Renesas RZ/G2L MTU3a counter
> > > driver")
> > > Cc: stable@vger.kernel.org
> > > Reviewed-by: Cosmin Tanislav <cosmin-gabriel.tanislav.xa@renesas.com>
> > > Signed-off-by: Li Youhong <liyouhong@kylinos.cn>
> > > ---
> > > v2:
> > > - Add Cc: stable@vger.kernel.org.
> > > - v1:
> > > https://lore.kernel.org/all/20261008020506.211566-1-dayou5941@163.com/
> > >
> > > drivers/counter/rz-mtu3-cnt.c | 7 +++++--
> > > 1 file changed, 5 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/counter/rz-mtu3-cnt.c
> > > b/drivers/counter/rz-mtu3-cnt.c index 7bfb6979193c..61fbeb122851
> > > 100644
> > > --- a/drivers/counter/rz-mtu3-cnt.c
> > > +++ b/drivers/counter/rz-mtu3-cnt.c
> > > @@ -506,8 +506,11 @@ static int rz_mtu3_count_enable_write(struct counter_device *counter,
> > > if (enable) {
> > > pm_runtime_get_sync(counter->parent);
> > > ret = rz_mtu3_initialize_counter(counter, count->id);
> > > - if (ret == 0)
> > > - priv->count_is_enabled[count->id] = true;
> > > + if (ret < 0) {
> > > + pm_runtime_put(counter->parent);
> > > + goto exit;
> > > + }
> > > + priv->count_is_enabled[count->id] = true;
> > > } else {
> > > rz_mtu3_terminate_counter(counter, count->id);
> > > priv->count_is_enabled[count->id] = false;
> > > --
> > > 2.25.1
> > >
V> >
> > This patch seems similar to another we're considering for ti-eqep.[^1] In that patch, runtime PM is
> > managed via devm which allows us to remove the explicit PM unwind on failures and have them implicitly
> > handled when the device resource is released. Should we use the same approach for rz-mtu-cnt?
>
> Here we save power, clock is turned on/off during counter enable/disable.
> On TI case, they enable it during the probe which unnecessarily waste power.
> Even disable case, the clock is on.
>
> Cheers,
> Biju
I suppose you are right. There is no need to keep the clocks powered if
the counter is disabled because we are no longer counting.
William Breathitt Gray.
prev parent reply other threads:[~2026-10-31 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 14:28 Li Youhong
2026-10-31 16:04 ` Biju Das
2026-10-31 16:28 ` William Breathitt Gray
2026-10-31 16:34 ` Biju Das
2026-10-31 18:21 ` William Breathitt Gray [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=20261031182120.3646747-1-wbg@kernel.org \
--to=wbg@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=cosmin-gabriel.tanislav.xa@renesas.com \
--cc=dayou5941@163.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=liyouhong@kylinos.cn \
--cc=stable@vger.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®