linux.git/include/linux/mmc, branch v4.3

mmc: block: skip trim for some kingston eMMCs

2015-08-27T12:50:52+00:00

For some mass production of kingston eMMCs which adopt Phison's
firmware will meet an unrecoverable data conrruption occasionally
if performing trim due to a firmware bug confirmed by vendor. We
found it on Intel-C3230RK platform. So we add fixup of broken trim
for it.

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

mmc: dw_mmc: add quirk for broken data transfer over scheme

2015-08-17T10:45:28+00:00

This patch add a new quirk to add a s/w timer to notify the driver
to terminate current transfer and report a data timeout to the core,
if DTO interrupt does NOT come within the given time.

dw_mmc call mmc_request_done func to finish transfer depends on
DTO interrupt. If DTO interrupt does not come in sending data state,
the current transfer will be blocked.

We got the reply from synopsys:
There are two counters but both use the same value of [31:8] bits.
Data timeout counter doesn't wait for stop clock and you should get
DRTO even when the clock is not stopped.
Host Starvation timeout counter is triggered with stop clock condition.

This means that host should get DRTO and DTO interrupt.

But this case really exists, when driver reads tuning data from
card on RK3288-pink2 board. I measured waveforms by oscilloscope
and found that card clock was always on and data lines were always
holded high level in sending data state.

There are two possibility that data over interrupt doesn't come in
reading data state on RK3X SoCs:
- get command done interrupt, but doesn't get any data-related interrupt.
- get data error interrupt, but doesn't get data over interrupt.

Signed-off-by: Addy Ke 
Signed-off-by: Heiko Stuebner 
Signed-off-by: Jaehoon Chung

mmc: dw_mmc: remove the unused blk_setting

2015-08-17T10:45:27+00:00

"blk_setting" doesn't use anywhere.

Signed-off-by: Jaehoon Chung

mmc: dw_mmc: fix pio mode when internal dmac is enabled

2015-08-17T10:44:43+00:00

The dw_mci_init_dma() may decide to not use dma, but pio instead, caused
by things like wrong dma settings in the system.

Till now the code dw_mci_init_slot() always assumed that dma is available
when CONFIG_MMC_DW_IDMAC was defined, ignoring the host->use_dma var
set during dma init.

So when now the dma init failed for whatever reason, the transfer sizes
would still be set for dma transfers, especially including the maximum
block-count calculated from host->ring_size and resulting in a

[    4.991109] ------------[ cut here ]------------
[    4.991111] kernel BUG at drivers/mmc/core/core.c:256!
[    4.991113] Internal error: Oops - BUG: 0 [#1] SMP ARM

because host->ring_size is 0 in this case and the slot init code uses
the wrong code to calculate the values.

Fix this by selecting the correct calculations using the host->use_dma
variable instead of the CONFIG_MMC_DW_IDMAC config option.

Signed-off-by: Heiko Stuebner 
Signed-off-by: Jaehoon Chung

mmc: sdio: avoid using NULL sdio_irq_thread pointer

2015-08-17T09:32:46+00:00

For Freescale QorIQ LS1021AQDS board, there is a SDIO interrupt
in the process of resume without inserting SD adapter because of
some unknown issue. But the driver doesn't assign sdio_irq_thread
pointer. This will block the resume of kernel. This patch is used
to avoid using NULL sdio_irq_thread pointer.

Signed-off-by: Yangbo Lu 
Signed-off-by: Ulf Hansson

mmc: core: Optimize case for exactly one erase-group budget

2015-08-17T09:32:39+00:00

In the (not so unlikely) case that the mmc controller timeout budget is
enough for exactly one erase-group, the simplification of allowing one
sector has an enormous performance penalty. We optimize this special case
by introducing a flag that prohibits erase-group boundary crossing, so
that we can allow trimming more than one sector at a time.

Signed-off-by: David Jander 
Signed-off-by: Ulf Hansson

mmc: mediatek: Add Mediatek MMC driver

2015-06-18T07:20:48+00:00

Add Mediatek MMC driver code
Support eMMC/SD/SDIO

Signed-off-by: Chaotian Jing 
Signed-off-by: Ulf Hansson

mmc: sdhci-pci: Add support for drive strength selection for SPT

2015-06-01T07:07:14+00:00

Implement the select_drive_strength callback to provide
drive strength selection for Intel SPT.

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

mmc: mmc: Add driver strength selection

2015-06-01T07:07:14+00:00

Add the ability to set eMMC driver strength
for HS200 and HS400.

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

mmc: mmc: Read card's valid driver strength mask

2015-06-01T07:07:13+00:00

In preparation for supporing drive strength selection
for eMMC, read the card's valid driver strengths.

Note that though the SD spec uses the term "drive strength",
the JEDEC eMMC spec uses the term "driver strength".

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