linux-toradex.git/include/linux/mmc/core.h, branch v3.0.16

mmc: core: Use CMD23 for multiblock transfers when we can.

2011-05-25T20:48:46+00:00

CMD23-prefixed instead of open-ended multiblock transfers
have a performance advantage on some MMC cards.

Signed-off-by: Andrei Warkentin 
Signed-off-by: Chris Ball

mmc: core: Add mmc CMD+ACMD passthrough ioctl

2011-05-25T01:02:54+00:00

Allows appropriately-privileged applications to send CMD (normal) and ACMD
(application-specific; preceded with CMD55) commands to cards/devices on
the mmc bus.  This is primarily useful for enabling the security
functionality built in to every SD card.

It can also be used as a generic passthrough (e.g. to enable virtual
machines to control mmc bus devices directly).  However, this use case has
not been tested rigorously.  Generic passthrough testing was only conducted
for a few non-security opcodes to prove the feasibility of the passthrough.

Since any opcode can be sent using this passthrough, it is very possible to
render the card/device unusable.  Applications that use this ioctl must
have CAP_SYS_RAWIO.

Security commands tested on TI PCIxx12 (SDHCI), Sigma Designs SMP8652 SoC,
TI OMAP3621/OMAP3630 SoC, Samsung S5PC110 SoC, Qualcomm MSM7200A SoC.

Signed-off-by: John Calixto 
Reviewed-by: Andrei Warkentin 
Reviewed-by: Arnd Bergmann 
Signed-off-by: Chris Ball

mmc: core: Allow setting CMD timeout for CMD6 (SWITCH).

2011-05-25T01:01:13+00:00

CMD6 is an R1B-type command, where DAT is used as busy. Depending
on register written using CMD6, timeout value can be different
as per spec.

Signed-off-by: Andrei Warkentin 
Signed-off-by: Chris Ball

mmc: core: Rename erase_timeout to cmd_timeout_ms.

2011-05-25T01:01:05+00:00

Renames erase_timeout to cmd_timeout_ms inside struct mmc_command.
First step to making host honor timeouts for non-data-transfer
commands. Cleans up erase timeout code.

Signed-off-by: Andrei Warkentin 
Signed-off-by: Chris Ball

mmc: core: export function mmc_do_release_host()

2011-03-17T19:35:11+00:00

When using mmc_try_claim_host the corresponding release
function is mmc_do_release_host, which then also must
be exported.

Reviewed-by: Jonas Aberg 
Reviewed-by: Sebastian Rasmussen 
Signed-off-by: Ulf Hansson 
Signed-off-by: Linus Walleij 
Signed-off-by: Chris Ball

mmc: Fixes for Dual Data Rate (DDR) support

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

The DDR support patch needs the following fixes:

- The block driver does not need to know about DDR, any more
  than it needs to know about bus width.
- Not only the card must be switched to DDR mode.  The host
  controller must also be configured, which is done through
  the 'set_ios()' function.
- Do not set the DDR mode state until after the switch command
  is successful.
- Setting block length is not supported in DDR mode.  Make that
  a core function and change the other place it is used (mmc_test)
  also.

Signed-off-by: Adrian Hunter 
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: 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

mmc: allow host claim / release nesting

2009-09-23T14:39:33+00:00

This change allows the MMC host to be claimed in situations where the host
may or may not have already been claimed.  Also 'mmc_try_claim_host()' is
now exported.

Signed-off-by: Adrian Hunter 
Acked-by: Matt Fleming 
Cc: Ian Molton 
Cc: "Roberto A. Foglietta" 
Cc: Jarkko Lavinen 
Cc: Denis Karpov 
Cc: Pierre Ossman 
Cc: Philip Langdale 
Cc: "Madhusudhan" 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

mmc: Add mmc_vddrange_to_ocrmask() helper function

2008-12-31T17:18:13+00:00

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 
Signed-off-by: Pierre Ossman