From: Chris Clayton via Bugspray Bot <bugbot@kernel.org>
To: linux-mmc@vger.kernel.org, ulf.hansson@linaro.org
Subject: Re: RTS5229 built in card reader not detected after Linux 5.0.x
Date: Wed, 22 Jan 2025 15:45:19 +0000 [thread overview]
Message-ID: <20250122-b204003c13-13740ac23e02@bugzilla.kernel.org> (raw)
In-Reply-To: <20250122-b204003c0-5776b9acf361@bugzilla.kernel.org>
Chris Clayton writes via Kernel.org Bugzilla:
This bug is a year old now, so here's some more diagnostics that may also act as a ping for the developer who created the regression to fix it, please.
lspci on Ubuntu 20.04 running on Intel NUC6CAYH. Kernel is 5.4.0-39-generic.
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)
Subsystem: Intel Corporation RTS5229 PCI Express Card Reader
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 255
Region 0: Memory at 91300000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s unlimited, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s (ok), Width x1 (ok)
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+, NROPrPrP-, LTR-
10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt-, EETLPPrefix-
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS-, TPHComp-, ExtTPHComp-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
AtomicOpsCtl: ReqEn-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
Capabilities: [140 v1] Device Serial Number 00-00-00-01-00-4c-e0-00
Kernel modules: rtsx_pci
View: https://bugzilla.kernel.org/show_bug.cgi?id=204003#c13
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
next prev parent reply other threads:[~2025-01-22 15:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 15:45 RTS5229 built in card reader not detected after Linux 5.0.x josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` David Lindstrom via Bugspray Bot
2025-01-22 15:45 ` David Lindstrom via Bugspray Bot
2025-01-22 15:45 ` David Lindstrom via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` josiahspore via Bugspray Bot
2025-01-22 15:45 ` Scott Brown via Bugspray Bot
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot [this message]
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot
2025-01-22 15:45 ` Yannis via Bugspray Bot
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot
2025-01-22 15:45 ` Scott Brown via Bugspray Bot
2025-01-22 15:45 ` Scott Brown via Bugspray Bot
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot
2025-01-22 15:45 ` Yannis via Bugspray Bot
2025-01-22 15:45 ` Scott Brown via Bugspray Bot
2025-01-22 15:45 ` Doug Miles via Bugspray Bot
2025-01-22 15:45 ` Chris Clayton via Bugspray Bot
2025-01-22 15:45 ` i.chryssochoos via Bugspray Bot
2025-01-22 15:45 ` Roger Heflin via Bugspray Bot
2025-01-22 15:45 ` Michael Garofalo via Bugspray Bot
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=20250122-b204003c13-13740ac23e02@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=linux-mmc@vger.kernel.org \
--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.