linux-stable.git/drivers/mmc/core, branch linux-4.8.y

mmc: mmc: Use 500ms as the default generic CMD6 timeout

2016-11-18T09:51:46+00:00

commit fe1b5700c70faac6e027982d59667bc6020de5a8 upstream.

In the eMMC 4.51 version of the spec, an EXT_CSD field called
GENERIC_CMD6_TIME[248] was added. This allows cards to specify the maximum
time it may need to move out from its busy state, when a CMD6 command has
been sent.

In cases when the card is compliant to versions < 4.51 of the eMMC spec,
obviously the core needs to use a fall-back value for this timeout, which
currently is set to 10 minutes. This value is completely in the wrong range
and importantly in some cases it causes a card initialization to take more
than 10 minute to complete.

Earlier this scenario was avoided as the mmc core used CMD13 to poll the
card, to find out when it stopped signaling busy. Commit 08573eaf1a70
("mmc: mmc: do not use CMD13 to get status after speed mode switch")
changed this behavior.

Instead of reverting that commit, which would cause other issues, let's
instead start by picking a simple solution for the problem, by using a
500ms default generic CMD6 timeout.

The reason for using exactly 500ms, comes from observations that shows it's
quite common for cards to specify 250ms. 500ms is two times that value so
likely it should be enough for most cards.

Fixes: 08573eaf1a70 ("mmc: mmc: do not use CMD13 to get status after speed
mode switch")
Signed-off-by: Ulf Hansson 
Tested-by: Stephen Boyd 
Tested-by: Linus Walleij 
Signed-off-by: Greg Kroah-Hartman

mmc: core: switch to 1V8 or 1V2 for hs400es mode

2016-10-28T07:45:30+00:00

commit 1720d3545b772c49b2975eeb3b8f4d3f56dc2085 upstream.

When introducing hs400es, I didn't notice that we haven't
switched voltage to 1V2 or 1V8 for it. That happens to work
as the first controller claiming to support hs400es, arasan(5.1),
which is designed to only support 1V8. So the voltage is fixed to 1V8.
But it actually is wrong, and will not fit for other host controllers.
Let's fix it.

Fixes: commit 81ac2af65793ecf ("mmc: core: implement enhanced strobe support")
Signed-off-by: Shawn Lin 
Reviewed-by: Douglas Anderson 
Signed-off-by: Ulf Hansson 
Signed-off-by: Greg Kroah-Hartman

mmc: Change the max discard sectors and erase response when HW busy detect

2016-07-25T09:11:08+00:00

When mmc host HW supports busy signalling (using R1B as response), don't
use the host->max_busy_timeout as the limitation when deciding the max
discard sectors, which we inform the generic BLOCK layer about. Instead,
let's use at least one preferred erase size as the max discard sectors.

In cases when the host controller supports HW busy signalling and the
timeout for the erase operation doesn't exceed the max_busy_timeout, we
keep the R1B response, otherwise we prevent the host from doing HW busy
detection by converting to a R1 response.

Signed-off-by: Baolin Wang 
Signed-off-by: Ulf Hansson

mmc: core: Extend sysfs with DSR register

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

Export DSR register through sysfs same as we did for the CID, CSD and
OCR registers.

Signed-off-by: Bojan Prtvar 
Signed-off-by: Ulf Hansson

mmc: core: expose MMC_CAP2_NO_* to dt

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

The reason for why we expose these to dt is that some of
the controller is unable to send special cmd type due to
the hw limitation.

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

mmc: core: Extend sysfs with OCR register

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

Registers CID and CSD are already exported through sysfs so let's make
this interface complete by adding missing OCR register.

Signed-off-by: Bojan Prtvar 
Reviewed-by: Wolfram Sang 
Signed-off-by: Ulf Hansson

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: Disable HPI for certain Hynix eMMC cards

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

Certain Hynix eMMC 4.41 cards might get broken when HPI feature is used
and hence this patch disables the HPI feature for such buggy cards.

As some of the other features like BKOPs/Cache/Sanitize are dependent on
HPI feature, those features would also get disabled if HPI is disabled.

Signed-off-by: Pratibhasagar V 
Signed-off-by: Subhash Jadavani 
[gdavis: Forward port and cleanup]
Signed-off-by: George G. Davis 
Signed-off-by: Ulf Hansson

mmc: core: Only change mode if mmc_select_bus_width() is successful

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

mmc_select_bus_width() returns bus width (4 or 8) on success or
zero if unsupported. So only change mode if setting the bus width
is successful.

Signed-off-by: Peter Griffin 
Signed-off-by: Ulf Hansson