linux.git/drivers/mmc/core, branch v2.6.29 Linux kernel source tree mmc: fix data timeout for SEND_EXT_CSD 2009-03-08T13:46:04+00:00 Adrian Hunter adrian.hunter@nokia.com 2009-02-10T14:32:33+00:00 cda56ac29f2d8288d62978272856884d26e0b47b Commit 0d3e0460f307e84904968aad6cff97bd688583d8 "MMC: CSD and CID timeout values" inadvertently broke the timeout for the MMC command SEND_EXT_CSD. This patch puts it back again. Depending on the characteristics of the controller, this bug may prevent the use of MMC cards. Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com> Signed-off-by: Pierre Ossman <drzeus@drzeus.cx> 
Commit 0d3e0460f307e84904968aad6cff97bd688583d8
"MMC: CSD and CID timeout values" inadvertently broke
the timeout for the MMC command SEND_EXT_CSD.

This patch puts it back again.

Depending on the characteristics of the controller,
this bug may prevent the use of MMC cards.

Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
mmc: warn about voltage mismatches 2008-12-31T18:27:18+00:00 David Brownell dbrownell@users.sourceforge.net 2008-12-31T17:50:30+00:00 f6e10b865c3ea56bdaa8c6ecfee313b997900dbb Get rid of a silent failure mode when the MMC/SD host doesn't support the voltages needed to operate a given card, by adding a warning. A 3.3V host and a 3.0V card, for example, no longer need to mysteriously just not work at all. This isn't the best diagnostic; ideally it would also tell what voltage the card and host support (and not just by dumping the bitmasks). Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Pierre Ossman <drzeus@drzeus.cx> 
Get rid of a silent failure mode when the MMC/SD host doesn't
support the voltages needed to operate a given card, by
adding a warning.  A 3.3V host and a 3.0V card, for example,
no longer need to mysteriously just not work at all.

This isn't the best diagnostic; ideally it would also tell
what voltage the card and host support (and not just by
dumping the bitmasks).

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
mmc: Add mmc_vddrange_to_ocrmask() helper function 2008-12-31T17:18:13+00:00 Anton Vorontsov avorontsov@ru.mvista.com 2008-11-26T19:54:17+00:00 86e8286a0e48663e1e86a5884b30a6d05de2993a This function sets the OCR mask bits according to provided voltage ranges. Will be used by the mmc_spi OpenFirmware bindings. Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com> Signed-off-by: Pierre Ossman <drzeus@drzeus.cx> 
This function sets the OCR mask bits according to provided voltage
ranges. Will be used by the mmc_spi OpenFirmware bindings.

Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
mmc: Add 8-bit bus width support 2008-12-31T17:18:12+00:00 Jarkko Lavinen jarkko.lavinen@nokia.com 2008-11-17T12:35:21+00:00 b30f8af3358b5c66be223e3a9f3d11b3d02b4a8f Signed-off-by: Jarkko Lavinen <jarkko.lavinen@nokia.com> Signed-off-by: Pierre Ossman <drzeus@drzeus.cx> 
Signed-off-by: Jarkko Lavinen <jarkko.lavinen@nokia.com>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
mmc: struct device - replace bus_id with dev_name(), dev_set_name() 2008-11-08T20:37:46+00:00 Kay Sievers kay.sievers@vrfy.org 2008-11-08T20:37:46+00:00 d1b268630875a7713b5d468a0c03403c5b721c8e Acked-by: Greg Kroah-Hartman <gregkh@suse.de> Signed-Off-By: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by: Pierre Ossman <drzeus@drzeus.cx> 
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-Off-By: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
mmc: increase SD write timeout for crappy cards 2008-11-08T20:36:59+00:00 Pierre Ossman drzeus@drzeus.cx 2008-10-26T11:37:25+00:00 493890e75d98810a3470b4aae23be628ee5e9667 It seems that some cards are slightly out of spec and occasionally will not be able to complete a write in the alloted 250 ms [1]. Incease the timeout slightly to allow even these cards to function properly. [1] http://lkml.org/lkml/2008/9/23/390 Signed-off-by: Pierre Ossman <drzeus@drzeus.cx> 
It seems that some cards are slightly out of spec and occasionally
will not be able to complete a write in the alloted 250 ms [1].
Incease the timeout slightly to allow even these cards to function
properly.

[1] http://lkml.org/lkml/2008/9/23/390

Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
MMC: CSD and CID timeout values 2008-10-12T09:04:37+00:00 Matthew Fleming matthew.fleming@imgtec.com 2008-10-02T11:24:05+00:00 0d3e0460f307e84904968aad6cff97bd688583d8 The MMC spec states that the timeout for accessing the CSD and CID registers is 64 clock cycles. Signed-off-by: Matthew Fleming <matthew.fleming@imgtec.com> Signed-off-by: Pierre Ossman <drzeus@drzeus.cx> 
The MMC spec states that the timeout for accessing the CSD and CID
registers is 64 clock cycles.

Signed-off-by: Matthew Fleming <matthew.fleming@imgtec.com>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
sdio: high-speed support 2008-10-12T09:04:34+00:00 Pierre Ossman drzeus@drzeus.cx 2008-08-31T15:22:46+00:00 d16f57700475f670ca2828c150a34fa7102a05fc Signed-off-by: Pierre Ossman <drzeus@drzeus.cx> 
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
sdio: give sdio irq thread a host specific name 2008-10-12T09:04:30+00:00 Pierre Ossman drzeus@drzeus.cx 2008-08-31T11:42:00+00:00 6501ff604a5ae18697c9b4cd40a7738d3a68e7fe There is one thread per host controller so make sure they all get unique names. Signed-off-by: Pierre Ossman <drzeus@drzeus.cx> 
There is one thread per host controller so make sure they all get
unique names.

Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
sdio: make sleep on error interruptable 2008-10-12T09:04:28+00:00 Pierre Ossman drzeus@drzeus.cx 2008-08-31T11:38:54+00:00 e633b7bcec8e26991d489a11615acf7674efbaf4 Make sure we can be woken from the forced sleep that is done on errors. Removing a card often results in -ENOMEDIUM or -EILSEQ so we previously locked up the removal process for a second. We could completely exit on -ENOMEDIUM, but it might be a transient glitch so treat it like any other error. Signed-off-by: Pierre Ossman <drzeus@drzeus.cx> 
Make sure we can be woken from the forced sleep that is done on errors.
Removing a card often results in -ENOMEDIUM or -EILSEQ so we previously
locked up the removal process for a second.

We could completely exit on -ENOMEDIUM, but it might be a transient
glitch so treat it like any other error.

Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>