linux-stable.git/drivers/mmc/core, branch v3.17

mmc: Do not advertise secure discard if it is blacklisted

2014-07-26T09:13:39+00:00

Currently when the device secure discard implementation is
blacklisted (MMC_QUIRK_SEC_ERASE_TRIM_BROKEN quirk is set)
instead of secure discard we're going to do normal discard,
which is wrong.

When the secure discard is known to be broken we should just
disallow it entirely and not advertise this functionality to
the user. Fix it.

Also move mmc_fixup_device() in from of mmc_blk_alloc() so we
can get quirks set before we attempt to set queue information.

Signed-off-by: Lukas Czerner 
Acked-by: Jaehoon Chung 
Signed-off-by: Ulf Hansson

mmc: Allow forward compatibility for eMMC

2014-07-09T09:26:11+00:00

As stated by the eMMC 5.0 specification, a chip should not be rejected
only because of the revision stated in the EXT_CSD_REV field of the
EXT_CSD register.

Remove the control on this value, the control of the CSD_STRUCTURE field
should be sufficient to reject future incompatible changes.

Signed-off-by: Romain Izard 
Signed-off-by: Ulf Hansson

mmc: sd: warn if card stays busy during init

2014-07-09T09:26:07+00:00

The initialization of some SD-cards fails because the card never
leaves the busy state. Aid trouble shooting by indicating this in the
kernel log.

Signed-off-by: Johan Rudholm 
Signed-off-by: Ulf Hansson

mmc: quirks: Fixup debug message

2014-07-09T09:26:03+00:00

There is no need for an output like this:
> mmcblk mmc1:0001: calling add_quirk_mmc+0x0/0x20
Instead use this one:
> mmcblk mmc1:0001: calling add_quirk_mmc

Signed-off-by: Alexander Stein 
Signed-off-by: Ulf Hansson

mmc: core: Remove redundant runtime_idle callback

2014-07-09T09:25:58+00:00

The runtime PM core handles a runtime_idle callback set to NULL as one
returning 0. So, let's just set it to NULL instead.

Signed-off-by: Ulf Hansson 
Acked-by: Jaehoon Chung

mmc: sdio_irq: rework sdio irq handling

2014-05-22T11:26:03+00:00

Rather than the SDIO support spawning it's own thread for handling card
interrupts, use the generic IRQ infrastructure for this, triggering it
from the host interface's interrupt handling directly.

This avoids a race between the parent thread waiting to receive an
interrupt response from the card, and the slow startup from the sdio
irq thread, which can occur as a result of high system load (eg, while
udev is running.)

Signed-off-by: Russell King 
Tested-by: Markus Pargmann 
Tested-by: Stephen Warren 
[Ulf Hansson] Resolved conflict
Signed-off-by: Ulf Hansson 
Signed-off-by: Chris Ball

mmc: core: Improve support for deferred regulators

2014-05-12T22:08:24+00:00

Callers of mmc_regulator_get_supply could benefit from knowing if either
of the regulators are present but not yet available.  Since callers do
not currently examine the return value, modify this function to return
zero or -EPROBE_DEFER if either regulator get returns the same.

Furthermore, since callers check vmmc/vqmmc using IS_ERR and can deal
with absent regulators, switch to devm_regulator_get_optional. This has
the added benefit of allowing this function to behave correctly even in
the !CONFIG_REGULATOR case such that the stub can be removed.

Signed-off-by: Tim Kryger 
Signed-off-by: Ulf Hansson 
Signed-off-by: Chris Ball

mmc: core: add DT bindings for eMMC HS400 1.8/1.2V

2014-05-12T22:08:10+00:00

Provide the option to configure these speed modes per host,
for those host driver's that can't distinguish this in runtime.
Specially, if host can support HS400, it means that host can also
support HS200.

Signed-off-by: Seungwon Jeon 
Signed-off-by: Ulf Hansson 
Signed-off-by: Chris Ball

mmc: add support for HS400 mode of eMMC5.0

2014-05-12T22:06:06+00:00

This patch adds HS400 mode support for eMMC5.0 device.  HS400 mode is high
speed DDR interface timing from HS200.  Clock frequency is up to 200MHz
and only 8-bit bus width is supported. In addition, tuning process of
HS200 is required to synchronize the command response on the CMD line
because CMD input timing for HS400 mode is the same as HS200 mode.

Signed-off-by: Seungwon Jeon 
Reviewed-by: Jackey Shen 
Tested-by: Jaehoon Chung 
Acked-by: Jaehoon Chung 
Signed-off-by: Ulf Hansson 
Signed-off-by: Chris Ball

mmc: rework selection of bus speed mode

2014-05-12T22:06:04+00:00

Current implementation for bus speed mode selection is too
complicated. This patch is to simplify the codes and remove
some duplicate parts.

The following changes are including:
* Adds functions for each mode selection(HS, HS-DDR, HS200 and etc)
* Rearranged the mode selection sequence with supported device type
* Adds maximum speed for HS200 mode(hs200_max_dtr)
* Adds field definition for HS_TIMING of EXT_CSD

Signed-off-by: Seungwon Jeon 
Tested-by: Jaehoon Chung 
Acked-by: Jaehoon Chung 
Signed-off-by: Ulf Hansson 
Signed-off-by: Chris Ball