From: Johan Hovold <johan@kernel.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: Guangshuo Li <lgs201920130244@gmail.com>,
Even Xu <even.xu@intel.com>, Xinpeng Sun <xinpeng.sun@intel.com>,
Benjamin Tissoires <bentiss@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Mark Pearson <mpearson-lenovo@squebb.ca>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] HID: intel-thc-hid: intel-quicki2c: fix autosuspend cleanup during teardown
Date: Thu, 20 Aug 2026 13:41:03 +0200 [thread overview]
Message-ID: <aobnz6lCxib4-5Ma@hovoldconsulting.com> (raw)
In-Reply-To: <p80oq2qq-5o87-01o7-qr0p-5op97414951s@xreary.bet>
Hi Jiri,
On Thu, Aug 20, 2026 at 01:33:16PM +0200, Jiri Kosina wrote:
> On Tue, 18 Aug 2026, Johan Hovold wrote:
>
> > > quicki2c_probe() calls pm_runtime_use_autosuspend(), but
> > > quicki2c_remove() does not call the matching
> > > pm_runtime_dont_use_autosuspend() during teardown.
> > >
> > > If the autosuspend delay is set to a negative value while autosuspend
> > > is enabled, the runtime PM core increments usage_count to prevent
> > > runtime suspend. Without calling pm_runtime_dont_use_autosuspend()
> > > during teardown, this reference is not dropped.
> >
> > I see that the HID ones have already been merged, but for the record:
> >
> > As I've explained elsewhere, this is just misleading. There is no usage
> > count leak here as the count is balanced whenever the user re-enables
> > autosuspend through sysfs (by writing a non-negative timeout).
> >
> > Drivers should clean up after themselves and disable autosuspend, but
> > this is more of a clean up than a fix and should not be backported.
> Looking at this now again in more detail, I believe the code change is
> actually OK, but the changelog is misleading. Or am I missing something?
Indeed, the change itself is fine, but the commit message is misleading
and these do not need to be backported.
Johan
next prev parent reply other threads:[~2026-08-20 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 14:57 Guangshuo Li
2026-08-10 0:53 ` Xu, Even
2026-08-14 13:13 ` Jiri Kosina
2026-08-18 8:39 ` Johan Hovold
2026-08-20 11:33 ` Jiri Kosina
2026-08-20 11:41 ` Johan Hovold [this message]
2026-08-20 11:47 ` Jiri Kosina
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=aobnz6lCxib4-5Ma@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=bentiss@kernel.org \
--cc=even.xu@intel.com \
--cc=jikos@kernel.org \
--cc=lgs201920130244@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=sakari.ailus@linux.intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=xinpeng.sun@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®