From: "Li Youhong" <dayou5941@163.com>
To: biju.das.jz@bp.renesas.com, wbg@kernel.org
Cc: linux-iio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Li Youhong <liyouhong@kylinos.cn>
Subject: [PATCH v2 0/3] counter: rz-mtu3-cnt: check clock and runtime PM errors
Date: Mon, 31 Aug 2026 13:44:04 +0800 [thread overview]
Message-ID: <20260831054407.1695146-1-dayou5941@163.com> (raw)
From: Li Youhong <liyouhong@kylinos.cn>
v1 checked only clk_prepare_enable() in probe/resume. Reviewers asked
to also handle pm_runtime_set_active() and all pm_runtime_get_sync()
call sites. Split into three patches, including a follow-up for a
pre-existing runtime PM usage leak on counter init failure.
Changes v1->v2
Link to v1: https://lore.kernel.org/all/20260828071123.179670-1-dayou5941@163.com/
- Also check pm_runtime_set_active() in probe
- Check pm_runtime_get_sync() everywhere
- New patch: put runtime PM ref if counter init fails after get
Li Youhong (3):
counter: rz-mtu3-cnt: check clk_prepare_enable() and
pm_runtime_set_active()
counter: rz-mtu3-cnt: check pm_runtime_get_sync() return values
counter: rz-mtu3-cnt: put runtime PM ref if counter init fails
drivers/counter/rz-mtu3-cnt.c | 119 +++++++++++++++++++++++++++-------
1 file changed, 94 insertions(+), 25 deletions(-)
--
2.25.1
next reply other threads:[~2026-08-31 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 5:44 Li Youhong [this message]
2026-08-31 5:44 ` [PATCH v2 1/3] counter: rz-mtu3-cnt: check clk_prepare_enable() and pm_runtime_set_active() Li Youhong
2026-08-31 5:44 ` [PATCH v2 2/3] counter: rz-mtu3-cnt: check pm_runtime_get_sync() return values Li Youhong
2026-09-03 6:53 ` Biju Das
2026-09-03 7:06 ` 李佑鸿
2026-08-31 5:44 ` [PATCH v2 3/3] counter: rz-mtu3-cnt: put runtime PM ref if counter init fails Li Youhong
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=20260831054407.1695146-1-dayou5941@163.com \
--to=dayou5941@163.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=liyouhong@kylinos.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