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:21 +0000 [thread overview]
Message-ID: <20250122-b204003c15-4a4081654d77@bugzilla.kernel.org> (raw)
In-Reply-To: <20250122-b204003c0-5776b9acf361@bugzilla.kernel.org>
Chris Clayton writes via Kernel.org Bugzilla:
I've done more investigating of this regression and I've narrowed it down to rtsx_pci_init_ocp() in drivers/misc/cardreader/rtsx_pcr.c. It is called by rtsx_pci_init_hw() (from the same source file. If a comment out that call, build and install the resultant kernel, the rts5229 reader and the card inserted in are detected and work fine. The machine is an Intel NUC Tall Arches Canyon NUC6CAYH Celeron J3455. I can't take this diagnosis any further because, as far as I can see, the only change the patch identified as the culprit (see comment 10 above) makes to rtsx_pci_init_ocp(), shouldn't be executed for the rts5229. So far, I've built and installed 5.7.12 and 5.4.54 the latter of which I am currently running on the machine. I think I tried an unpatched 5.7 series kernel earlier in my investagations and the card reader did not work. To be sure, I'll build an older 5.4 kernel that more closely matches the one currently included in Ubuntu 20.04, and check whether that works when rtsx_pc
i_init_ocp() is not called.
View: https://bugzilla.kernel.org/show_bug.cgi?id=204003#c15
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
2025-01-22 15:45 ` Chris Clayton 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 ` 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-b204003c15-4a4081654d77@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox