linux-toradex.git/drivers/mmc/core/sd.c, branch v3.7

mmc: core: reset signal voltage on power up

2012-07-22T19:25:53+00:00

Add a call to mmc_set_signal_voltage() to set signal voltage to 3.3v in
mmc_power_up so that we do not need to touch signal voltage setting in
mmc/sd/sdio init functions and rescan function.

For mmc/sd cards, when doing a suspend/resume cycle, consider the unsafe
resume case, the card will lose its power and when powered on again, we
will set signal voltage to 3.3v in mmc_power_up before its resume function
gets called, which will re-init the card.

And for sdio cards, when doing a suspend/resume cycle, consider the unsafe
resume case, the card will either lose its power or not depending on if it
wants to wakeup the host. If power is not maintained, it is the same case as
mmc/sd cards. If power is maintained, mmc_power_up will not be called and
the card's signal voltage will remain at the last setting.

Signed-off-by: Aaron Lu 
Tested-by: Venkatraman S 
Signed-off-by: Chris Ball

mmc: sd: Fix sd current limit setting

2012-07-22T19:25:52+00:00

Host has different current capabilities at different voltages, we need
to record these settings seperately. The defined voltages are 1.8/3.0/3.3.
For other voltages, we do not touch current limit setting.

Before we set the current limit for the sd card, find out the host's
operating voltage first and then find out the current capabilities of
the host at that voltage to set the current limit.

Signed-off-by: Aaron Lu 
Reviewed-by: Philip Rakity 
Signed-off-by: Chris Ball

mmc: core: Simplify and fix for SD switch processing

2012-07-22T19:25:47+00:00

In mmc_read_switch, just do a one time mode 0 switch command to get the
support bits information, no need to do multiple times as the support
bits do not change with different arguments.

And no need to check current limit support bits, as these bits are
fixed according to the signal voltage. If the signal voltage is 1.8V,
the support bits would be 0xf and if the signal voltage is 3.3V, the
support bits would be 0x01. We will check host's ability to set the
current limit.

Signed-off-by: Aaron Lu 
Signed-off-by: Chris Ball

mmc: core: correct invalid error checking

2012-07-21T04:02:24+00:00

The effect of the existing code is that we continue blindly when we
should warn about an invalid allocation unit.

Reported-by: dcb314@hotmail.com
Resolves-bug: https://bugzilla.kernel.org/show_bug.cgi?id=44061
Signed-off-by: Alan Cox 
Signed-off-by: Chris Ball

mmc: sdhci: only set 200mA support for 1.8v if 200mA is available

2012-07-21T04:02:23+00:00

max_current_caps can return 0 if not available from the sd controller.
If no regulator is present or the regulator specifies a current
less then 200ma, we no longer still set the 200mA caps bit anyway.

Signed-off-by: Philip Rakity 
Reviewed-by: Aaron Lu 
Signed-off-by: Chris Ball

mmc: core: return an error on suspend if mmc_deselect_cards fails

2012-06-06T13:49:47+00:00

When mmc_host is not spi mode, mmc/sd is doing mmc_deselect_cards().
mmc_deselect_cards could be returned error.
If returned error, we can know something wrong when enter suspend.

Signed-off-by: Jaehoon Chung 
Signed-off-by: Kyungmin Park 
Acked-by: Ulf Hansson 
Signed-off-by: Chris Ball

mmc: core: Fixup suspend/resume issues for UHS-I cards

2012-03-04T17:25:15+00:00

Even if cards supports 1.8V I/O voltage those should anyway be
initialized at 3.3V I/O according to (e)MMC, SD and SDIO specs.
Some eMMC and embedded SDIO devices are able to be initialized
at 1.8V as well, but it is better to be safe.

Do note that initialization in this context means that the card
has been completely powered off, otherwise the card will remain
at the last I/O voltage level that were negotitiated.

Due to the above being taken care of the suspend/resume issues
for UHS-I SD-cards has been fixed.

Signed-off-by: Ulf Hansson 
Acked-by: Philip Rakity 
Acked-by: Linus Walleij 
Tested-by: Subhash Jadavani 
Signed-off-by: Chris Ball

mmc: core: Ensure clocks are always enabled before host interaction

2012-02-14T01:38:58+00:00

Ensure clocks are always enabled before any interaction with the
host controller driver. This makes sure that there is no race
between host execution and the core layer turning off clocks
in different context with clock gating framework.

Signed-off-by: Sujit Reddy Thumma 
Acked-by: Linus Walleij 
Acked-by: Per Forlin 
Signed-off-by: Chris Ball

mmc: core: HS200 mode support for eMMC 4.5

2012-01-12T20:17:15+00:00

This patch adds the support of the HS200 bus speed for eMMC 4.5 devices.
The eMMC 4.5 devices have support for 200MHz bus speed. The function
prototype of the tuning function is modified to handle the tuning
command number which is different in sd and mmc case.

Signed-off-by: Girish K S 
Signed-off-by: Philip Rakity 
Signed-off-by: Chris Ball

mmc: allow upper layers to know immediately if card has been removed

2012-01-12T04:58:43+00:00

Add a function mmc_detect_card_removed() which upper layers can use to
determine immediately if a card has been removed. This function should
be called after an I/O request fails so that all queued I/O requests
can be errored out immediately instead of waiting for the card device
to be removed.

Signed-off-by: Adrian Hunter 
Acked-by: Sujit Reddy Thumma 
Signed-off-by: Chris Ball