linux.git/include/linux/mmc/card.h, branch v2.6.39

mmc: add MMC_QUIRK_BROKEN_CLK_GATING

2011-03-15T17:48:35+00:00

Some sdio card are not following sdio standard, and do not work
when the sdio bus's clock is gated.

To keep functionnality for all legacy driver, we turn this quirk on
for every sdio card.
Drivers needs to disable the quirk manually when someone verifies that
their supported card works with clock gating.

Signed-off-by: Pierre Tardy 
Acked-by: Ohad Ben-Cohen 
Signed-off-by: Chris Ball

mmc: add per device quirk placeholder

2011-03-15T17:48:33+00:00

Some cards have quirks valid for every platforms using current
platform quirk hooks leads to a lot of code and debug duplication.

So we inspire a bit from what exists in PCI subsystem and do our own
per vendorid/deviceid quirk.  We still drop the complexity of the pci
quirk system (with special section tables, and so on).
That can be added later if needed.

Signed-off-by: Pierre Tardy 
Acked-by: Linus Walleij 
Acked-by: Ohad Ben-Cohen 
Signed-off-by: Chris Ball

mmc: export eMMC4.4 enhanced area details to sysfs

2011-03-15T17:48:01+00:00

Enhanced area feature is a new feature defined in eMMC4.4 standard. This
user data area provides higher performance/reliability, at the expense
of using twice the effective media space due to the area using SLC.

The MMC driver now reads out the enhanced area offset and size and adds
them to the device attributes in sysfs. Enabling the enhanced area can
only be done once, and should be done in manufacturing. To use this
feature, bit ERASE_GRP_DEF should also be set.

Documentation/ABI/testing/sysfs-devices-mmc describes the two new
attributes.

Signed-off-by: Chuanxiao Dong 
Reviewed-by: Chris Ball 
Signed-off-by: Chris Ball

mmc: MMC 4.4 DDR support

2010-10-23T13:11:16+00:00

Add support for Dual Data Rate MMC cards as defined in the 4.4
specification.

Signed-off-by: Hanumath Prasad 
Cc: linux-mmc@vger.kernel.org
Acked-by: Linus Walleij 
Tested-by Zhangfei Gao 
Signed-off-by: Chris Ball

mmc: rename dev_to_mmc_card() to mmc_dev_to_card()

2010-10-23T13:11:12+00:00

Global symbols should use their subsystem name in a prefixed fashion.

Signed-off-by: Andy Shevchenko 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Chris Ball

mmc: make mmc_dev_to_card() macro public

2010-10-23T13:11:12+00:00

Conversion from struct device to struct mmc_card is used more than in one
place.  Due to this it's better to have public macro for such thing.

Signed-off-by: Andy Shevchenko 
Cc: Adrian Hunter 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Chris Ball

mmc: add erase, secure erase, trim and secure trim operations

2010-08-12T15:43:30+00:00

SD/MMC cards tend to support an erase operation.  In addition, eMMC v4.4
cards can support secure erase, trim and secure trim operations that are
all variants of the basic erase command.

SD/MMC device attributes "erase_size" and "preferred_erase_size" have been
added.

"erase_size" is the minimum size, in bytes, of an erase operation.  For
MMC, "erase_size" is the erase group size reported by the card.  Note that
"erase_size" does not apply to trim or secure trim operations where the
minimum size is always one 512 byte sector.  For SD, "erase_size" is 512
if the card is block-addressed, 0 otherwise.

SD/MMC cards can erase an arbitrarily large area up to and
including the whole card.  When erasing a large area it may
be desirable to do it in smaller chunks for three reasons:

    1. A single erase command will make all other I/O on the card
       wait.  This is not a problem if the whole card is being erased, but
       erasing one partition will make I/O for another partition on the
       same card wait for the duration of the erase - which could be a
       several minutes.

    2. To be able to inform the user of erase progress.

    3. The erase timeout becomes too large to be very useful.
       Because the erase timeout contains a margin which is multiplied by
       the size of the erase area, the value can end up being several
       minutes for large areas.

"erase_size" is not the most efficient unit to erase (especially for SD
where it is just one sector), hence "preferred_erase_size" provides a good
chunk size for erasing large areas.

For MMC, "preferred_erase_size" is the high-capacity erase size if a card
specifies one, otherwise it is based on the capacity of the card.

For SD, "preferred_erase_size" is the allocation unit size specified by
the card.

"preferred_erase_size" is in bytes.

Signed-off-by: Adrian Hunter 
Acked-by: Jens Axboe 
Cc: Kyungmin Park 
Cc: Madhusudhan Chikkature 
Cc: Christoph Hellwig 
Cc: Ben Gardiner 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

sdio: allow non-standard SDIO cards

2010-08-11T15:59:04+00:00

There are some chips (like TI WL12xx series) that can be interfaced over
SDIO but don't support the SDIO specification, meaning that they are
missing CIA (Common I/O Area) with all it's registers.  Current Linux SDIO
implementation relies on those registers to identify and configure the
card, so non-standard cards can not function and cause lots of warnings
from the core when it reads invalid data from non-existent registers.

After this patch, init_card() host callback can now set new quirk
MMC_QUIRK_NONSTD_SDIO, which means that SDIO core should not try to access
any standard SDIO registers and rely on init_card() to fill all SDIO
structures instead.  As those cards are usually embedded chips, all the
required information can be obtained from machine board files by the host
driver when it's called through init_card() callback.

Signed-off-by: Grazvydas Ignotas 
Cc: Adrian Hunter 
Cc: Tony Lindgren 
Cc: Bob Copeland 
Cc: Kalle Valo 
Cc: Madhusudhan Chikkature 
Cc: Kishore Kadiyala 
Cc: Russell King 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

mmc: implement SD-combo (IO+mem) support

2010-08-11T15:59:03+00:00

Signed-off-by: Michal Miroslaw 
Cc: Adrian Hunter 
Cc: Chris Ball 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

mmc: recognize CSD structure

2010-08-11T15:59:02+00:00

The eMMC spec 4.4 and 4.3 + additional feature chips has CSD structure
version 3 and version 3 have to check the CSD_STRUCTURE byte in the
EXT_CSD register.

Also fix EXT_CSD revision message.

[akpm@linux-foundation.org: fix comment, per Chris Ball]
Signed-off-by: Kyungmin Park 
Cc: Adrian Hunter 
Cc: Chris Ball 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds