linux-stable.git/include/linux/mmc/host.h, branch v4.8

mmc: core: Allow hosts to specify non-support for MMC commands

2016-07-25T08:34:47+00:00

Host drivers which needs to valdiate for non-supported MMC
commands and returnn error code for such requests.

To improve and simplify the behaviour, let's invent MMC_CAP2_NO_MMC
which these host drivers can set to tell the mmc core to skip sending MMC
commands during card initialization.

Signed-off-by: Shawn Lin 
Signed-off-by: Ulf Hansson

mmc: core: Allow hosts to specify non-support for SD commands

2016-07-25T08:34:22+00:00

There are host drivers which needs to valdiate for non-supported SD
commands and returnn error code for such requests.

To improve and simplify the behaviour, let's invent MMC_CAP2_NO_SD
which these host drivers can set to tell the mmc core to skip sending SD
commands during card initialization.

Signed-off-by: Ulf Hansson

mmc: core: implement enhanced strobe support

2016-07-25T08:34:05+00:00

Controllers use data strobe line to latch data from devices
under hs400 mode, but not for cmd line. So since emmc 5.1, JEDEC
introduces enhanced strobe mode for latching cmd response from
emmc devices to host controllers. This new feature is optional,
so it depends both on device's cap and host's cap to decide
whether to use it or not.

Signed-off-by: Shawn Lin 

Reviewed-by: Jaehoon Chung 
Tested-by: Douglas Anderson 
Tested-by: Jaehoon Chung 
Acked-by: Adrian Hunter 
Signed-off-by: Ulf Hansson

mmc: core: add mmc-hs400-enhanced-strobe support

2016-07-25T08:34:05+00:00

This patch introduce mmc-hs400-enhanced-strobe for platforms
which want to enable enhanced strobe function from DT if the
mmc host controller claims to support enhanced strobe.

Signed-off-by: Shawn Lin 

Reviewed-by: Douglas Anderson 
Tested-by: Jaehoon Chung 
Signed-off-by: Ulf Hansson

mmc: core: Add a facility to "pause" re-tuning

2016-05-17T14:54:26+00:00

Re-tuning is not possible when switched to the RPMB
partition.  However re-tuning should not be needed
if re-tuning is done immediately before switching,
a small set of operations is done, and then we
immediately switch back to the main partition.

To ensure that re-tuning can't be done for a short
while, add a facility to "pause" re-tuning.

The existing facility to hold / release re-tuning
is used but it also flags re-tuning as needed to cause
re-tuning before the next command (which will be the
switch to RPMB).

We also need to "unpause" in the recovery path, which
is catered for by adding it to mmc_retune_disable().

Signed-off-by: Adrian Hunter 
Signed-off-by: Ulf Hansson

mmc: host: add note that set_ios needs to handle 0Hz properly

2016-05-02T08:33:14+00:00

While here, refactor the comments so that they are before the
declaration they are referring to.

Signed-off-by: Wolfram Sang 
Signed-off-by: Ulf Hansson

mmc: core: Introduce MMC_CAP2_NO_SDIO cap

2015-12-22T10:32:13+00:00

This patch introduce a new MMC_CAP2_NO_SDIO cap used to tell the mmc
core to not send SDIO specific commands.

Signed-off-by: Carlo Caione 
Signed-off-by: Ulf Hansson

mmc: core: Refactor code to register the MMC PM notifier

2015-12-22T10:32:04+00:00

Instead of checking for "#ifdef" directly in the code, let's invent a pair
of mmc core functions to deal with register/unregister the MMC PM notifier
block. Implement stubs for these functions when CONFIG_PM_SLEEP is unset,
as in that case the PM notifiers isn't used.

Signed-off-by: Ulf Hansson

mmc: core: Remove MMC_CAP_RUNTIME_RESUME as it's redundant

2015-12-22T10:32:03+00:00

Signed-off-by: Ulf Hansson

mmc: core: Add mmc_regulator_set_vqmmc()

2015-10-26T15:00:10+00:00

This adds logic to the MMC core to set VQMMC.  This is expected to be
called by MMC drivers like dw_mmc as part of (or instead of) their
start_signal_voltage_switch() callback.

A few notes:

* When setting the signal voltage to 3.3V we do our best to make VQMMC
  and VMMC match.  It's been reported that this makes some old cards
  happy since they were tested back in the day before UHS when VQMMC
  and VMMC were provided by the same regulator.  A nice side effect of
  this is that we don't end up on the hairy edge of VQMMC (2.7V),
  which some EEs claim is a little too close to the minimum for
  comfort.
  This is done in two steps. At first we try to find a VQMMC within
  a 0.3V tolerance of VMMC and if this is not supported by the
  supplying regulator we try to find a suitable voltage within the
  whole 2.7V-3.6V area of the spec.

* The two step approach is currently necessary, as the used
  regulator_set_voltage_triplet(min, target, max) uses a simple
  implementation that just tries two basic steps:
	regulator_set_voltage(target, max);
	regulator_set_voltage(min, target);
  So with only one step with 2.7-3.6V borders, if a suitable voltage
  is a bit below VMMC, we would directly get the lowest 2.7V
  which some boards (like Rockchips) don't like at all.

* When setting the signal voltage to 1.8V or 1.2V we aim for that
  specific voltage instead of picking the lowest one in the range.

* We very purposely don't print errors in mmc_regulator_set_vqmmc().
  There are cases where the MMC core will try several different
  voltages and we don't want to pollute the logs.

Signed-off-by: Douglas Anderson 
Signed-off-by: Heiko Stuebner 
Signed-off-by: Ulf Hansson