[PATCH AUTOSEL 6.19-5.15] mmc: rtsx_pci: add quirk to disable MMC_CAP_AGGRESSIVE_PM for RTS525A

[Sasha Levin]

From: Matthew Schwartz <matthew.schwartz@xxxxxxxxx>

[ Upstream commit 5f0bf80cc5e04d31eeb201683e0b477c24bd18e7 ]

Using MMC_CAP_AGGRESSIVE_PM on RTS525A card readers causes game
performance issues when the card reader comes back from idle into active
use. This can be observed in Hades II when loading new sections of the
game or menu after the card reader puts itself into idle, and presents
as a 1-2 second hang.

Add EXTRA_CAPS_NO_AGGRESSIVE_PM quirk to allow cardreader drivers to
opt-out of aggressive PM, and set it for RTS525A.

Closes: https://lore.kernel.org/linux-mmc/ff9a7c20-f465-4afa-bf29-708d4a52974a@xxxxxxxxx/
Signed-off-by: Matthew Schwartz <matthew.schwartz@xxxxxxxxx>
Link: https://patch.msgid.link/20260103204226.71752-1-matthew.schwartz@xxxxxxxxx
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Sasha Levin <sashal@xxxxxxxxxx>
---

LLM Generated explanations, may be completely bogus:

### Summary Analysis

**What the commit does:**
This commit adds a device-specific quirk for the Realtek RTS525A card
reader to disable `MMC_CAP_AGGRESSIVE_PM`. When aggressive PM is enabled
on this device, it powers down the card reader after 10 seconds of idle,
and re-tuning when waking up causes 1-2 second hangs that are user-
visible and impact performance.

**Does it fix a real bug?**
Yes. The aggressive PM behavior on RTS525A causes real, user-observable
1-2 second hangs during normal use. This was reported by a real user
with concrete reproduction steps (playing a game that loads data from a
micro SD card). The "Closes:" tag links to a real mailing list report.

**Stable kernel criteria assessment:**

1. **Obviously correct and tested**: The change follows an existing
   pattern (`EXTRA_CAPS_NO_MMC` is the exact same kind of quirk flag).
   The author tested it on affected hardware.

2. **Fixes a real bug**: Yes - user-visible performance degradation (1-2
   second hangs) on specific hardware.

3. **Important issue**: It's a usability issue rather than a
   crash/security issue. However, hardware quirks for broken behavior
   are explicitly allowed in stable.

4. **Small and contained**: The change is minimal - 3 new lines of code
   plus a new flag definition. It only affects RTS525A devices and
   doesn't change behavior for any other hardware.

5. **No new features**: This is a hardware quirk/workaround, which is an
   explicitly allowed exception to the "no new features" rule.

6. **Clean application**: The change builds on existing infrastructure
   (`extra_caps` flags) that exists in all stable trees since v5.11.

**Risk assessment:**
- **Very low risk**: The quirk only affects RTS525A devices
  (`PID_525A`). All other devices are completely unaffected.
- The code pattern is identical to existing quirks
  (`EXTRA_CAPS_NO_MMC`).
- The worst case if the quirk is wrong is slightly higher power
  consumption on RTS525A (no aggressive PM = card reader stays powered).

**Dependencies:**
None. The change uses existing infrastructure (`extra_caps`,
`CHK_PCI_PID`, `PID_525A`) that has been present since before v5.11.

### Verification

- **git log** showed `rtd3_en` / `MMC_CAP_AGGRESSIVE_PM` was introduced
  in commit `5b4258f6721f4` (v5.11), confirming all current stable trees
  have the affected code.
- **git tag --contains** confirmed the runtime PM commit is in stable
  trees (p-5.15, p-6.1, p-6.12).
- **Grep for EXTRA_CAPS_** confirmed the existing quirk flag pattern
  (NO_MMC at bit 7, SD_EXPRESS at bit 8, new flag at bit 9 - clean
  progression).
- **lore.kernel.org fetch** confirmed the bug report describes real
  user-reported 1-2 second hangs on RTS525A with concrete reproduction
  steps.
- **Code review** verified the change only adds a condition check and
  flag - no behavioral change for non-RTS525A devices.
- The commit was signed off by Greg Kroah-Hartman, the stable tree
  maintainer, indicating it went through proper review.
- Could NOT verify whether any stable tree has already picked this up
  (unverified, but not relevant to the YES/NO decision).

### Conclusion

This is a textbook hardware quirk for a specific device with a real,
user-reported issue. It follows existing patterns in the codebase, is
minimal in scope, and has zero risk to other devices. Hardware quirks
are explicitly listed as appropriate for stable backporting. The
affected code exists in all current stable trees (5.15+).

**YES**

 drivers/misc/cardreader/rts5249.c | 3 +++
 drivers/mmc/host/rtsx_pci_sdmmc.c | 4 ++--
 include/linux/rtsx_pci.h          | 1 +
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/drivers/misc/cardreader/rts5249.c b/drivers/misc/cardreader/rts5249.c
index 38aefd8db452a..87d576a03e68e 100644
--- a/drivers/misc/cardreader/rts5249.c
+++ b/drivers/misc/cardreader/rts5249.c
@@ -78,6 +78,9 @@ static void rtsx_base_fetch_vendor_settings(struct rtsx_pcr *pcr)
 	if (CHK_PCI_PID(pcr, PID_524A) || CHK_PCI_PID(pcr, PID_525A))
 		pcr->rtd3_en = rtsx_reg_to_rtd3_uhsii(reg);
 
+	if (CHK_PCI_PID(pcr, PID_525A))
+		pcr->extra_caps |= EXTRA_CAPS_NO_AGGRESSIVE_PM;
+
 	if (rtsx_check_mmc_support(reg))
 		pcr->extra_caps |= EXTRA_CAPS_NO_MMC;
 	pcr->sd30_drive_sel_3v3 = rtsx_reg_to_sd30_drive_sel_3v3(reg);
diff --git a/drivers/mmc/host/rtsx_pci_sdmmc.c b/drivers/mmc/host/rtsx_pci_sdmmc.c
index 4db3328f46dfb..8df60000b5b41 100644
--- a/drivers/mmc/host/rtsx_pci_sdmmc.c
+++ b/drivers/mmc/host/rtsx_pci_sdmmc.c
@@ -1497,8 +1497,8 @@ static void realtek_init_host(struct realtek_pci_sdmmc *host)
 	mmc->caps = MMC_CAP_4_BIT_DATA | MMC_CAP_SD_HIGHSPEED |
 		MMC_CAP_MMC_HIGHSPEED | MMC_CAP_BUS_WIDTH_TEST |
 		MMC_CAP_UHS_SDR12 | MMC_CAP_UHS_SDR25;
-	if (pcr->rtd3_en)
-		mmc->caps = mmc->caps | MMC_CAP_AGGRESSIVE_PM;
+	if (pcr->rtd3_en && !(pcr->extra_caps & EXTRA_CAPS_NO_AGGRESSIVE_PM))
+		mmc->caps |= MMC_CAP_AGGRESSIVE_PM;
 	mmc->caps2 = MMC_CAP2_NO_PRESCAN_POWERUP | MMC_CAP2_FULL_PWR_CYCLE |
 		MMC_CAP2_NO_SDIO;
 	mmc->max_current_330 = 400;
diff --git a/include/linux/rtsx_pci.h b/include/linux/rtsx_pci.h
index 3c5689356004e..f6122349c00ec 100644
--- a/include/linux/rtsx_pci.h
+++ b/include/linux/rtsx_pci.h
@@ -1230,6 +1230,7 @@ struct rtsx_pcr {
 #define EXTRA_CAPS_MMC_8BIT		(1 << 5)
 #define EXTRA_CAPS_NO_MMC		(1 << 7)
 #define EXTRA_CAPS_SD_EXPRESS		(1 << 8)
+#define EXTRA_CAPS_NO_AGGRESSIVE_PM	(1 << 9)
 	u32				extra_caps;
 
 #define IC_VER_A			0
-- 
2.51.0