From: Joshua Crofts <joshua.crofts1@gmail.com>
To: Abel Vesa <abelvesa@kernel.org>, Peng Fan <peng.fan@nxp.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: linux-clk@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] clk: imx: add missing pm_runtime_dont_use_autosuspend() calls
Date: Tue, 15 Sep 2026 10:33:43 +0000 [thread overview]
Message-ID: <20260915103345.1334-1-joshua.crofts1@gmail.com> (raw)
Several drivers in the clk subsystem forget to call dont_use_autosuspend()
on teardown or error, causing potential resource leaks. This series adds
the missing calls.
The offending drivers were found using a semantic patch for Coccinelle
I'm working on [1].
[1] https://lore.kernel.org/all/20260915064327.1377-1-joshua.crofts1@gmail.com/
Joshua Crofts (2):
clk: imx: clk-imx8qxp-lpcg: add missing
pm_runtime_dont_use_autosuspend()
clk: imx: scu: add missing pm_runtime_dont_use_autosuspend() call
drivers/clk/imx/clk-imx8qxp-lpcg.c | 1 +
drivers/clk/imx/clk-scu.c | 2 ++
2 files changed, 3 insertions(+)
--
2.47.3
next reply other threads:[~2026-09-15 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 10:33 Joshua Crofts [this message]
2026-09-15 10:33 ` [PATCH 1/2] clk: imx: clk-imx8qxp-lpcg: add missing pm_runtime_dont_use_autosuspend() Joshua Crofts
2026-09-15 10:33 ` [PATCH 2/2] clk: imx: scu: add missing pm_runtime_dont_use_autosuspend() call Joshua Crofts
2026-09-16 9:24 ` [PATCH 0/2] clk: imx: add missing pm_runtime_dont_use_autosuspend() calls Johan Hovold
2026-09-16 16:11 ` Frank Li
2026-09-17 8:24 ` Joshua Crofts
2026-09-17 8:42 ` Joshua Crofts
2026-09-17 16:25 ` Frank Li
2026-09-17 17:15 ` Joshua Crofts
2026-09-17 18:36 ` Frank Li
2026-09-18 7:25 ` Joshua Crofts
2026-09-18 14:42 ` Frank Li
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=20260915103345.1334-1-joshua.crofts1@gmail.com \
--to=joshua.crofts1@gmail.com \
--cc=Frank.Li@nxp.com \
--cc=abelvesa@kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=jbrunet+clk@baylibre.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@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®