Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: "i.chryssochoos 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:32 +0000	[thread overview]
Message-ID: <20250122-b204003c26-388b1c9760a9@bugzilla.kernel.org> (raw)
In-Reply-To: <20250122-b204003c0-5776b9acf361@bugzilla.kernel.org>

i.chryssochoos writes via Kernel.org Bugzilla:

Hi,
I don't have access to 6.2. I'm currently on Ubuntu 22.04 with kernel
5.15.0-76-generic (on the same box as back in 2020) and behavior is
mixed:

I tried a Samsung Evo 256GB (U3, V30 etc.)  and had an error:
[5189171.233955] mmc1: cannot verify signal voltage switch
[5189171.568328] mmc1: error -110 whilst initialising SD card

Switching to a 10+ year old 8GB SDHC got things working:
[5189234.395708] mmc1: new high speed SDHC card at address 0007
[5189234.412143] mmcblk1: mmc1:0007 SD08G 7.50 GiB 

Reinserting the 256GB card worked:
[5189290.073393] mmc1: cannot verify signal voltage switch
[5189290.191013] mmc1: new ultra high speed SDR104 SDXC card at address
59b4
[5189290.191462] mmcblk1: mmc1:59b4 EE4S5 239 GiB 

After a warm reboot (card left in slot during this), it's still
recognized without the voltage switch issue message being printed:
[2.053896] mmc1: new ultra high speed SDR104 SDXC card at address 59b4
[2.057427] mmcblk1: mmc1:59b4 EE4S5 239 GiB 

All in all, the problem of the reader not working at all is (still)
fixed but it looks like some hardware registers or similar are not
properly initialized at boot?  Maybe using an older/simpler/etc. card
brings them to a working state?

Happy to supply more details etc.

Yannis

On Sat, 2023-07-01 at 15:29 +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=204003
> 
> --- Comment #25 from Chris Clayton (chris2553@googlemail.com) ---
> I no longer have the hardware, so cant help any further.
> 
> Chris
> 
> On Sat, 1 Jul 2023, 14:22 , <bugzilla-daemon@kernel.org> wrote:
> 
> > https://bugzilla.kernel.org/show_bug.cgi?id=204003
> > 
> > Doug Miles (dougmiles42@gmail.com) changed:
> > 
> >            What    |Removed                     |Added
> > 
> > -------------------------------------------------------------------
> > ---------
> >                  CC|                           
> > |dougmiles42@gmail.com
> > 
> > --- Comment #24 from Doug Miles (dougmiles42@gmail.com) ---
> > Bumping this, because it seems to have died on the vine and is
> > still an
> > issue
> > in kernel 6.2, as far as I can tell.
> > 
> > --
> > You may reply to this email to add a comment.
> > 
> > You are receiving this mail because:
> > You are on the CC list for the bug.
>

View: https://bugzilla.kernel.org/show_bug.cgi?id=204003#c26
You can reply to this message to join the discussion.
-- 
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)


  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
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 [this message]
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-b204003c26-388b1c9760a9@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