Skip to contentSkip to conversation

sdhci needs card to be present when loading module.

DISCUSSION Greg KH 3 participants 3 messages May 12, 2006 – May 13, 2006

lore
Share & tools
lore

Greg KH

author
#0 lore raw

In the 2.6.17-rc4 kernel (and 2.6.17-rc1), on my laptop, if you load the sdhci driver with no SD card in the slot, it never seems to be able to detect the insertion of a new card later on.

However, if I load the module with a card present. Removing it and then plugging it (or another one) in later seems to work just fine.

Is this expected?

Any kernel log messages I can provide to help with this?

thanks,

greg k-h

#1 lore raw
Quoted 9 lines · Greg KH

In the 2.6.17-rc4 kernel (and 2.6.17-rc1), on my laptop, if you load the sdhci driver with no SD card in the slot, it never seems to be able to detect the insertion of a new card later on.

However, if I load the module with a card present. Removing it and then plugging it (or another one) in later seems to work just fine.

Is this expected?

No, this is a bug (hardware probably as I cannot find anything in the specs that can even be remotely related). The chances of getting any help from the manufacturer are slim at best. I've already contacted all the major ones and requested erratas, but so far not a single reply.

Quoted 1 line

Any kernel log messages I can provide to help with this?

Not really, no. Since I assume this controller works fine in Windows, I'm guessing it needs a very particular init sequence. It might have something to do with the ios calls that are made when the slot is empty.

If you have the time, you could try adding some code that will make the driver ignore ios calls until a card is inserted.

Rgds
Pierre

#2 lore raw
In reply to Greg KH

Hi Greg,

Quoted 6 lines

In the 2.6.17-rc4 kernel (and 2.6.17-rc1), on my laptop, if you load the sdhci driver with no SD card in the slot, it never seems to be able to detect the insertion of a new card later on.

However, if I load the module with a card present. Removing it and then plugging it (or another one) in later seems to work just fine.

I had the same problem with my Ricoh controller (in an IBM X41) and the latest sdhci driver from mainline. Try the audit patch from Pierre, but be careful. For me it freezes the machine on eject, because of an endless loop waiting for some hardware state to change.

Regards

Marcel