linux.git/include/linux/mmc, branch v3.6

mmc: card: Skip secure erase on MoviNAND; causes unrecoverable corruption.

2012-09-04T17:58:10+00:00

For several MoviNAND eMMC parts, there are known issues with secure
erase and secure trim.  For these specific MoviNAND devices, we skip
these operations.

Specifically, there is a bug in the eMMC firmware that causes
unrecoverable corruption when the MMC is erased with MMC_CAP_ERASE
enabled.

References:

http://forum.xda-developers.com/showthread.php?t=1644364
https://plus.google.com/111398485184813224730/posts/21pTYfTsCkB#111398485184813224730/posts/21pTYfTsCkB

Signed-off-by: Ian Chen 
Reviewed-by: Namjae Jeon 
Acked-by: Jaehoon Chung 
Reviewed-by: Linus Walleij 
Cc: stable  [3.0+]
Signed-off-by: Chris Ball

Merge branch 'next' of git://git.infradead.org/users/vkoul/slave-dma

2012-07-25T00:12:54+00:00

Pull slave-dmaengine update from Vinod Koul:
 "This time we have a new dmaengine driver from the tegra folks.  Also
  we have Guennadi's cleanup of sh drivers which incudes a library for
  sh drivers.  And the usual odd fixes in bunch of drivers and some nice
  cleanup of dw_dmac from Andy."

Fix up conflicts in drivers/mmc/host/sh_mmcif.c

* 'next' of git://git.infradead.org/users/vkoul/slave-dma: (46 commits)
  dmaengine: Cleanup logging messages
  mmc: sh_mmcif: switch to the new DMA channel allocation and configuration
  dma: sh: provide a migration path for slave drivers to stop using .private
  dma: sh: use an integer slave ID to improve API compatibility
  dmaengine: shdma: prepare to stop using struct dma_chan::private
  sh: remove unused DMA device pointer from SIU platform data
  ASoC: siu: don't use DMA device for channel filtering
  dmaengine: shdma: (cosmetic) simplify a static function
  dmaengine: at_hdmac: add a few const qualifiers
  dw_dmac: use 'u32' for LLI structure members, not dma_addr_t
  dw_dmac: mark dwc_dump_lli inline
  dma: mxs-dma: Export missing symbols from mxs-dma.c
  dma: shdma: convert to the shdma base library
  ASoC: fsi: prepare for conversion to the shdma base library
  usb: renesas_usbhs: prepare for conversion to the shdma base library
  ASoC: siu: prepare for conversion to the shdma base library
  serial: sh-sci: prepare for conversion to the shdma base library
  mmc: sh_mobile_sdhi: prepare for conversion to the shdma base library
  mmc: sh_mmcif: remove unneeded struct sh_mmcif_dma, prepare to shdma conversion
  dma: shdma: prepare for conversion to the shdma base library
  ...

mmc: sd: Fix sd current limit setting

2012-07-22T19:25:52+00:00

Host has different current capabilities at different voltages, we need
to record these settings seperately. The defined voltages are 1.8/3.0/3.3.
For other voltages, we do not touch current limit setting.

Before we set the current limit for the sd card, find out the host's
operating voltage first and then find out the current capabilities of
the host at that voltage to set the current limit.

Signed-off-by: Aaron Lu 
Reviewed-by: Philip Rakity 
Signed-off-by: Chris Ball

mmc: sdhci: Introduce new flag SDHCI_USING_RETUNING_TIMER

2012-07-22T19:25:49+00:00

Add a new flag of SDHCI_USING_RETUNING_TIMER to represent if the host
is using a retuning timer for the card inserted.

This flag is set when the host does tuning the first time for the card
and the host's retuning mode is 1. This flag is used afterwards whenever
needs to decide if the host is currently using a retuning timer.

This flag is cleared when the card is removed in sdhci_reinit.

The set/clear of the flag and the start/stop of the retuning timer is
associated with the card's init/remove time, so there is no need to
touch it when the host is to be removed as at that time the card should
have already been removed.

Signed-off-by: Aaron Lu 
Reviewed-by: Girish K S 
Reviewed-by: Philip Rakity 
Signed-off-by: Chris Ball

mmc: sdhci: Allow caps[1] to be set via SDHCI_QUIRK_MISSING_CAPS

2012-07-22T19:25:44+00:00

Currently only the capability_0 register can be set if
SDHCI_QUIRK_MISSING_CAPS is defined.  This is a problem when
the capability_1 register also needs changing.  Use the quirk
SDHCI_QUIRK_MISSING_CAPS to allow both registers to be set.

Redefining caps[1] is useful when the board design does not
support 1.8v vccq so UHS modes are not available.  The code that
calls sdhci_add_host can then detect this condition and adjust
the caps so the UHS mode will not be attempted on UHS cards.

Signed-off-by: Philip Rakity 
Signed-off-by: Chris Ball

mmc: sdhci: only set 200mA support for 1.8v if 200mA is available

2012-07-21T04:02:23+00:00

max_current_caps can return 0 if not available from the sd controller.
If no regulator is present or the regulator specifies a current
less then 200ma, we no longer still set the 200mA caps bit anyway.

Signed-off-by: Philip Rakity 
Reviewed-by: Aaron Lu 
Signed-off-by: Chris Ball

mmc: sh_mmcif: support generic card-detection

2012-07-21T04:02:22+00:00

Extend the sh_mmcif driver to support GPIO card detection, provided by the
slot function module. The original .get_cd() platform callback is also
preserved for now.

Signed-off-by: Guennadi Liakhovetski 
Signed-off-by: Chris Ball

mmc: sh_mobile_sdhi: support caps2 flags

2012-07-21T04:02:19+00:00

Let SDHI platforms specify mmc_host::caps2 flags in their platform data.

Signed-off-by: Guennadi Liakhovetski 
Signed-off-by: Chris Ball

mmc: core: add WP pin handler to slot functions

2012-07-21T04:02:18+00:00

Card Write-Protect pin is often implemented, using a GPIO, which makes
it simple to provide a generic handler for it.

Signed-off-by: Guennadi Liakhovetski 
Signed-off-by: Chris Ball

mmc: core: convert slot functions to managed allocation

2012-07-21T04:02:17+00:00

This prepares for the addition of further slot functions.

Signed-off-by: Guennadi Liakhovetski 
Signed-off-by: Chris Ball