linux.git/drivers/mmc/core, branch v4.6-rc2

mmc: core: remove redundant memset of sdio_read_cccr

2016-03-17T13:54:41+00:00

When initializing sdio card, we get struct mmc_card
from mmc_alloc_card which allocates it by kzalloc. So we
don't need another memset while reading cccr.

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

mmc: core: remove redundant memset of mmc_decode_cid

2016-03-17T13:54:41+00:00

When initializing sd or sdio card, we get struct mmc_card
from mmc_alloc_card which allocates it by kzalloc. So we don't
need another memset while decoding cid.

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

mmc: core: report tuning command execution failure reason

2016-02-29T10:03:08+00:00

Print the error code when the tuning command fails.  This allows the
reason for the failure to be reported, which aids debugging.

Signed-off-by: Russell King 
Signed-off-by: Ulf Hansson

mmc: core: improve mmc_of_parse_voltage() to return better status

2016-02-29T10:03:07+00:00

Improve mmc_of_parse_voltage()'s return values so that drivers can tell
whether a voltage-range specification was present, and whether it has
been successfully parsed, or there was an error while parsing.

We return a negative errno when parsing fails, zero if no voltage-range
specification is present, or one if a voltage-range specification is
successfully parsed.

No users need modifying as no users check the return value.

Signed-off-by: Russell King 
Signed-off-by: Ulf Hansson

mmc: core: shut up "voltage-ranges unspecified" pr_info()

2016-02-29T10:03:07+00:00

Each time a driver such as sdhci-esdhc-imx is probed, we get a info
printk complaining that the DT voltage-ranges property has not been
specified.

However, the DT binding specifically says that the voltage-ranges
property is optional.  That means we should not be complaining that
DT hasn't specified this property: by indicating that it's optional,
it is valid not to have the property in DT.

Silence the warning if the property is missing.

Signed-off-by: Russell King 
Signed-off-by: Ulf Hansson

mmc: sanitize 'bus width' in debug output

2016-02-29T10:02:56+00:00

The bus width is sometimes the actual bus width, and sometimes indices
to different arrays encoding the bus width. In my debugging case "2"
could mean 8-bit as well as 4-bit, which was extremly confusing. Let's
use the human-readable actual bus width in all places.

Signed-off-by: Wolfram Sang 
Signed-off-by: Ulf Hansson

mmc: core: use the defined function to check whether card is removable

2016-02-29T10:02:56+00:00

In linux/mmc/host.h, mmc_card_is_removable() is already defined.
There is no reason that it doesn't use.

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

mmc: make MAN_BKOPS_EN message a debug

2016-02-29T10:02:53+00:00

IMO this info is only useful for developers. Most users won't need this
information, since there is not much they can do about it.

Signed-off-by: Wolfram Sang 
Signed-off-by: Ulf Hansson

mmc: core: enable mmc host device to suspend/resume asynchronously

2016-02-29T10:02:51+00:00

This patch enables mmc hosts to suspend/resume asynchronously.
This will improve system suspend/resume speed. After applying
this patch and enabling all mmc hosts' child devices to
suspend/resume asynchronously on ASUS T100TA, the system
suspend-to-idle time is reduced from 1645ms to 1107ms, and the
system resume time is reduced from 940ms to 914ms.

Signed-off-by: Zhonghui Fu 
Acked-by: Venu Byravarasu 
Signed-off-by: Ulf Hansson

mmc: debugfs: Add a restriction to mmc debugfs clock setting

2016-02-29T10:02:49+00:00

Clock frequency values written to an mmc host should not be less than
the minimum clock frequency which the mmc host supports.

Signed-off-by: Yuan Juntao 
Signed-off-by: Pawel Wodkowski 
Signed-off-by: Ulf Hansson