Comment 3 for bug 2040157

The upstream bug report ends in bisecting to:

commit 69304c8d285b77c9a56d68f5ddb2558f27abf406
Author: Ricky WU <email address hidden>
Date: Tue Jul 25 09:10:54 2023 +0000

     misc: rtsx: judge ASPM Mode to set PETXCFG Reg

     commit 101bd907b4244a726980ee67f95ed9cafab6ff7a upstream.

     ASPM Mode is ASPM_MODE_CFG need to judge the value of clkreq_0
     to set HIGH or LOW, if the ASPM Mode is ASPM_MODE_REG
     always set to HIGH during the initialization.

     Cc: <email address hidden>
     Signed-off-by: Ricky Wu <email address hidden>
     Link:
https://<email address hidden>
     Signed-off-by: Greg Kroah-Hartman <email address hidden>

  drivers/misc/cardreader/rts5227.c | 2 +-
  drivers/misc/cardreader/rts5228.c | 18 ------------------
  drivers/misc/cardreader/rts5249.c | 3 +--
  drivers/misc/cardreader/rts5260.c | 18 ------------------
  drivers/misc/cardreader/rts5261.c | 18 ------------------
  drivers/misc/cardreader/rtsx_pcr.c | 5 ++++-
  6 files changed, 6 insertions(+), 58 deletions(-)

All the changes are not directly in the nvme code but seem to have some influence there. One comment suggested to blacklist the resulting module "rtsx_pci". According to kernel-parameters.txt one can pass in a blacklist via "module_blacklist=rtsx_pci".