RFC rtsx_usb: runtime PM fixes before tray-reader detect rework
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | rtsx_usb: hold runtime PM during transfersdrivers/ | +31 | 2 replies | |
| 2/2 | rtsx_usb: avoid USB I/O in runtime autosuspenddrivers/ include/ | +10 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/2] rtsx_usb: runtime PM fixes before tray-reader detect rework
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(-)