From: Sean Rhodes <sean@starlabs.systems>
To: linux-kernel@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sean Rhodes <sean@starlabs.systems>,
Ulf Hansson <ulf.hansson@linaro.org>,
Ricky Wu <ricky_wu@realtek.com>, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-usb@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: [RFC PATCH 0/2] rtsx_usb: runtime PM fixes before tray-reader detect rework
Date: Mon, 13 Apr 2026 12:42:29 +0100 [thread overview]
Message-ID: <cover.1776080528.git.sean@starlabs.systems> (raw)
This is an RFC for the USB/cardreader side of the rtsx tray-reader issue.
Assuming the separate resume-reset fix has landed, this is the next step:
clean up runtime PM handling in the USB/cardreader layer before attempting
any further MMC-side detect changes.
Patch 1 holds a runtime PM reference across transfers and marks the device
busy afterwards.
Patch 2 avoids issuing USB register I/O from the runtime autosuspend path,
which can deadlock runtime PM and leave the device stuck in a suspending
state.
The remaining tray-reader false-detect problem likely needs event
qualification on the USB/cardreader side rather than MMC command probing
from ->get_cd(). Guidance on the right place for that logic would be
useful.
Sean Rhodes (2):
rtsx_usb: hold runtime PM during transfers
rtsx_usb: avoid USB I/O in runtime autosuspend
drivers/misc/cardreader/rtsx_usb.c | 49 +++++++++++++++++++++++-------
include/linux/rtsx_usb.h | 3 ++
2 files changed, 41 insertions(+), 11 deletions(-)
next reply other threads:[~2026-04-13 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 11:42 Sean Rhodes [this message]
2026-04-13 11:42 ` [RFC PATCH 1/2] rtsx_usb: hold runtime PM during transfers Sean Rhodes
2026-05-11 14:04 ` Ulf Hansson
2026-04-13 11:42 ` [RFC PATCH 2/2] rtsx_usb: avoid USB I/O in runtime autosuspend Sean Rhodes
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=cover.1776080528.git.sean@starlabs.systems \
--to=sean@starlabs.systems \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=ricky_wu@realtek.com \
--cc=tglx@linutronix.de \
--cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.