From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Cong Nguyen <congnt264@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Shawn Tu <shawnx.tu@intel.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: i2c: hi556: fix power leak on remove while runtime-active
Date: Mon, 28 Sep 2026 17:33:23 +0300 [thread overview]
Message-ID: <arp6s_vpgXx9RTMY@kekkonen.localdomain> (raw)
In-Reply-To: <20260928135140.2354361-1-congnt264@gmail.com>
Hi Cong,
Thanks for the patches.
On Mon, Sep 28, 2026 at 08:51:40PM +0700, Cong Nguyen wrote:
> hi556_remove() calls pm_runtime_disable() but never hi556_suspend().
> pm_runtime_disable() only blocks future auto suspend/resume, it
> doesn't force a final one -- if unbound while hi556_set_stream() is
> holding an outstanding PM reference (removed while still streaming),
> the device stays genuinely active with regulators/clock enabled
> forever after.
>
> probe()'s own error path already shows the right pairing (calls
> hi556_suspend() when powered on). Do the same in remove(), guarded by
> pm_runtime_status_suspended() so the common already-suspended case
> isn't suspended twice -- same guard sibling imx412.c's remove() uses.
>
> Moved remove() after suspend()/resume()'s definitions since it now
> calls them directly.
A few notes on this as the rest:
- The quality of this commit message needs to be improved.
- When you're sending a bunch of similar patches, please send them in a
single patchset.
- When moving functions around and then making changes to them, please do
this in two separate patches.
- If the device's PM runtime status isn't SUSPENDED in remove(), it needs
to be set SUSPENDED using pm_runtime_set_suspended(). Please do this
while making other PM runtime changes to the remove functions.
I'm marking these as "changes requested".
--
Kind regards,
Sakari Ailus
prev parent reply other threads:[~2026-09-28 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 13:51 Cong Nguyen
2026-09-28 14:33 ` Sakari Ailus [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=arp6s_vpgXx9RTMY@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=congnt264@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=shawnx.tu@intel.com \
/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®