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

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

mmc: core: Record card drive strength

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

In preparation for adding drive strength support
for eMMC, add drive_strength to struct mmc_card
to record the card drive strength for UHS-I modes
and HS200 / HS400. For eMMC this will be needed
when switching between HS200 and HS400.

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

mmc: core: Add 'card' to drive strength selection callback

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

In preparation for supporting also eMMC drive strength,
add the 'card' as a parameter so that the callback can
distinguish different types of cards if necessary.

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

mmc: core: Allow card drive strength to be different to host

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

Initialization of UHS-I modes for SD and SDIO cards
employs a callback to allow the host driver to
choose a drive strength value. Currently that
assumes the card drive strength and host driver
type must be the same value. Change to let the
callback make that decision and return both the
card drive strength and host driver type.

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

mmc: dw_mmc: Use core to handle absent write protect line

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

Use the new MMC_CAP2_NO_WRITE_PROTECT to let the core handle the case where
no write protect line is present instead of having custom driver code to
handle it.

dw_mci_of_get_slot_quirks() is slightly refactored to directly modify the
mmc_host capabilities instead of returning a quirk mask.

Signed-off-by: Lars-Peter Clausen 
Signed-off-by: Jaehoon Chung 
Signed-off-by: Ulf Hansson

mmc: Add support for disabling write-protect detection

2015-06-01T07:06:59+00:00

It is not uncommon to see systems where there is no physical write-protect
signal (e.g. when using eMMC or microSD card slots). For some controllers,
which have a dedicated write-protection detection logic (like SDHCI
controllers), the get_ro() callback can return bogus data in such a case.

Instead of handling this on a per controller basis this patch adds a new
capability flag to the MMC core that can be set to specify that the result
of get_ro() is invalid. When the flag is set the core will not call
get_ro() and assume that the card is always read-write.

Signed-off-by: Lars-Peter Clausen 
Signed-off-by: Ulf Hansson

mmc: host: Add facility to support re-tuning

2015-06-01T07:06:53+00:00

Currently, there is core support for tuning during
initialization. There can also be a need to re-tune
periodically (e.g. sdhci) or to re-tune after the
host controller is powered off (e.g. after PM
runtime suspend / resume) or to re-tune in response
to CRC errors.

The main requirements for re-tuning are:
  - ability to enable / disable re-tuning
  - ability to flag that re-tuning is needed
  - ability to re-tune before any request
  - ability to hold off re-tuning if the card is busy
  - ability to hold off re-tuning if re-tuning is in
  progress
  - ability to run a re-tuning timer

To support those requirements 7 members are added to struct
mmc_host:

  unsigned int		can_retune:1;	/* re-tuning can be used */
  unsigned int		doing_retune:1;	/* re-tuning in progress */
  unsigned int		retune_now:1;   /* do re-tuning at next req */
  int			need_retune;	/* re-tuning is needed */
  int			hold_retune;	/* hold off re-tuning */
  unsigned int		retune_period;  /* re-tuning period in secs */
  struct timer_list	retune_timer;	/* for periodic re-tuning */

need_retune is an integer so it can be set without needing
synchronization. hold_retune is a integer to allow nesting.

Various simple functions are provided to set / clear those
variables.

Subsequent patches take those functions into use.

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