linux.git/drivers/mmc, branch v2.6.17 Linux kernel source tree [MMC] Prevent au1xmmc.c breakage on non-Au1200 Alchemy 2006-06-04T16:40:58+00:00 Ralf Baechle ralf@linux-mips.org 2006-06-04T16:40:58+00:00 092d01e260da628b01d4229c31a296111e3cd97a The driver is selectable on other than Au1200 Alchemy systems but won't build nor work - there is no MMC hw. Signed-off-by: Ralf Baechle <ralf@linux-mips.org> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
The driver is selectable on other than Au1200 Alchemy systems but won't
build nor work - there is no MMC hw.

Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[MMC] Fix premature use of md->disk 2006-05-24T15:35:31+00:00 Pierre Ossman drzeus@drzeus.cx 2006-05-24T08:20:45+00:00 51c403274093767d6dc30703d67e9f0b255c7439 md->disk was being used in a debug message before it was allocated. Signed-off-by: Pierre Ossman <drzeus@drzeus.cx> Signed-off-by: Linus Torvalds <torvalds@osdl.org> 
md->disk was being used in a debug message before it was allocated.

Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
[ARM] 3531/1: i.MX/MX1 SD/MMC ensure, that clock are stopped before new command and cleanups 2006-05-19T20:48:03+00:00 Pavel Pisa ppisa@pikron.com 2006-05-19T20:48:03+00:00 2c171bf13423dc5293188cea7f6c2da1720926e2 Patch from Pavel Pisa There has been problems that for some paths that clock are not stopped during new command programming and initiation. Result is issuing of incorrect command to the card. Some other problems are cleaned too. Noisy report of known ERRATUM #4 has been suppressed. Signed-off-by: Pavel Pisa <pisa@cmp.felk.cvut.cz> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
Patch from Pavel Pisa

There has been problems that for some paths that clock are not stopped
during new command programming and initiation. Result is issuing
of incorrect command to the card. Some other problems are cleaned too.
Noisy report of known ERRATUM #4 has been suppressed.

Signed-off-by: Pavel Pisa <pisa@cmp.felk.cvut.cz>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[MMC] Move set_ios debugging into mmc.c 2006-05-04T17:22:51+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2006-05-04T17:22:51+00:00 920e70c5c603ada05dd480ca0ccc0ae12a5fdc39 Rather than having every driver duplicate the set_ios debugging, provide a single version in mmc.c which can be expanded as we add additional functionality. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
Rather than having every driver duplicate the set_ios debugging,
provide a single version in mmc.c which can be expanded as we
add additional functionality.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[MMC] Correct mmc_request_done comments 2006-05-04T12:51:45+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2006-05-04T12:51:45+00:00 fe10c6abea8bc83291a13e0580b3e4c355710b09 mmc_request_done should be called at the end of handling a request, not between the data and initial command parts of the request. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
mmc_request_done should be called at the end of handling a request, not
between the data and initial command parts of the request.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[MMC] PXA: reduce the number of lines PXAMCI debug uses 2006-05-02T19:18:53+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2006-05-02T19:18:53+00:00 d78e9079af7526c4661ff484322094832776ef41 There's no reason for the PXAMCI debug code to print so many lines - it causes the kernel buffer to overflow when trying to debug this driver. Remove some debug messages which are duplicated by core code, and combine other messages, resulting in fewer characters written to the kernel log. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
There's no reason for the PXAMCI debug code to print so many lines - it
causes the kernel buffer to overflow when trying to debug this driver.
Remove some debug messages which are duplicated by core code, and
combine other messages, resulting in fewer characters written to the
kernel log.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[MMC] PXA and i.MX: don't avoid sending stop command on error 2006-05-02T19:02:39+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2006-05-02T19:02:39+00:00 58741e8b3603e56c3699550e8bc89cb136329343 Always send a stop command at the end of a data transfer. If we avoid sending the stop command, some cards remain in data transfer mode, and refuse to accept further read/write commands. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
Always send a stop command at the end of a data transfer.  If we avoid
sending the stop command, some cards remain in data transfer mode, and
refuse to accept further read/write commands.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[MMC] extend data timeout for writes 2006-05-02T16:24:59+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2006-05-02T16:24:59+00:00 37be4e7809e0581db85387e126ae4da68c3d6286 The CSD contains a "read2write factor" which determines the multiplier to be applied to the read timeout to obtain the write timeout. We were ignoring this parameter, resulting in the possibility for writes being timed out too early. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
The CSD contains a "read2write factor" which determines the multiplier to
be applied to the read timeout to obtain the write timeout.  We were
ignoring this parameter, resulting in the possibility for writes being
timed out too early.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[ARM] 3485/1: i.MX: MX1 SD/MMC fix of unintentional double start possibility 2006-04-30T14:35:54+00:00 Pavel Pisa ppisa@pikron.com 2006-04-30T14:35:54+00:00 81d38428df26377c91e7e193aa4d2fdfdcda300a Patch from Pavel Pisa The clock starting imxmci_start_clock() function contains hardware issue workaround, which repeats start attempt, if SDHC does not react on the first trial. But the second start attempt can be taken even, if the first succeed and test code misses time limited clock running phase due to delay caused by schedule to other task or some another device interrupt. This change enables to detect such situation. The performance is not issue, because usually at full clock rate only about six loops in delay cycle are needed. Signed-off-by: Pavel Pisa <pisa@cmp.felk.cvut.cz> Acked-by: Sascha Hauer <s.hauer@pengutronix.de> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
Patch from Pavel Pisa

The clock starting imxmci_start_clock() function contains hardware
issue workaround, which repeats start attempt, if SDHC does not react on
the first trial. But the second start attempt can be taken even, if the
first succeed and test code misses time limited clock running phase
due to delay caused by schedule to other task or some another device
interrupt. This change enables to detect such situation.
The performance is not issue, because usually at full clock rate
only about six loops in delay cycle are needed.

Signed-off-by: Pavel Pisa <pisa@cmp.felk.cvut.cz>
Acked-by: Sascha Hauer <s.hauer@pengutronix.de>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[MMC] pxamci: fix data timeout calculation 2006-04-24T10:27:02+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2006-04-24T10:27:02+00:00 3d63abe56be2147891b3438cb3bd37a9be72bda7 The MMC layer gives us two parts for the timeout calculation - a fixed timeout in nanoseconds, and a card clock-speed dependent part. The PXA MMC hardware allows for a timeout based on the fixed host clock speed only. This resulted in some cards being given a short timeout, and therefore failing to work. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
The MMC layer gives us two parts for the timeout calculation - a fixed
timeout in nanoseconds, and a card clock-speed dependent part.

The PXA MMC hardware allows for a timeout based on the fixed host clock
speed only.  This resulted in some cards being given a short timeout,
and therefore failing to work.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>