linux-toradex.git/drivers/mmc/card, branch tegra-10.9.9

[tegra mmc] Generate mmcblk names based on controller.

2010-07-29T00:01:25+00:00

Generate mmcblk[%d] names based on sdhci controller instance numbers.
Bug 700011

Change-Id: I2be0c88f45cb2044306b1f8b8fe98ee95a800e0e
Reviewed-on: http://git-master.nvidia.com/r/4274
Reviewed-by: Jonathan Mayo 
Tested-by: Krishna Reddy 
Reviewed-by: Gary King

mmc_block: fix queue cleanup

2010-02-08T23:08:39+00:00

The main bug was that 'blk_cleanup_queue()' was called while the block
device could still be in use, for example, because the card was removed
while files were still open.

In addition, to be sure that 'mmc_request()' will get called for all new
requests (so it can error them out), the queue is emptied during cleanup.
This is done after the worker thread is stopped to avoid racing with it.

Finally, it is not a device error for this to be happening, so quiet the
(sometimes very many) error messages.

Signed-off-by: Adrian Hunter 
Cc: 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds 
Signed-off-by: San Mehat

mmc_block: fix probe error cleanup bug

2010-02-08T23:08:38+00:00

If mmc_blk_set_blksize() fails mmc_blk_probe() the request queue and its
thread have been set up and they need to be shut down properly before
putting the disk.

Signed-off-by: Jarkko Lavinen 
Signed-off-by: Adrian Hunter 
Cc: 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds 
Signed-off-by: San Mehat

mmc_block: add dev_t initialization check

2010-02-08T23:08:38+00:00

When a card is removed before mmc_blk_probe() has called add_disk(), then
the minor field is uninitialized and has value 0.  This caused
mmc_blk_put() to always release devidx 0 even if 0 was still in use.  Then
the next mmc_blk_probe() used the first free idx of 0, which oopses in
sysfs, since it is used by another card.

Signed-off-by: Anna Lemehova 
Signed-off-by: Adrian Hunter 
Cc: 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds 
Signed-off-by: San Mehat

mmc: block: Resume multi-block reads after transient read errors.

2010-02-08T23:08:36+00:00

Signed-off-by: Bentao Zou 
Signed-off-by: David Ding 
Signed-off-by: San Mehat

mmc: mmcblk: Add support for deferred SD bus resume

2010-02-08T23:08:31+00:00

Signed-off-by: San Mehat 

mmc: card: Add MMC_BLOCK_DEFERRED_RESUME option to Kconfig

Signed-off-by: San Mehat

const: make block_device_operations const

2009-09-22T14:17:25+00:00

Signed-off-by: Alexey Dobriyan 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

mmc_block: do not DMA to stack

2009-06-13T20:43:01+00:00

In the write recovery routine, the data to get from the card
is allocated from the stack. The DMA mapping documentation says
explicitly stack memory is not mappable by any of the DMA calls.

Change to using kmalloc() to allocate the memory for the result
from the card and then free it once we've finished with the
transaction.

[ Changed to GFP_KERNEL allocation - Pierre Ossman ]

Signed-off-by: Ben Dooks 
Signed-off-by: Pierre Ossman

block: Do away with the notion of hardsect_size

2009-05-22T21:22:54+00:00

Until now we have had a 1:1 mapping between storage device physical
block size and the logical block sized used when addressing the device.
With SATA 4KB drives coming out that will no longer be the case.  The
sector size will be 4KB but the logical block size will remain
512-bytes.  Hence we need to distinguish between the physical block size
and the logical ditto.

This patch renames hardsect_size to logical_block_size.

Signed-off-by: Martin K. Petersen 
Signed-off-by: Jens Axboe

Merge branch 'master' into for-2.6.31

2009-05-22T18:25:34+00:00

Conflicts:
	drivers/block/hd.c
	drivers/block/mg_disk.c

Signed-off-by: Jens Axboe