linux.git/drivers/mmc/core, branch v3.8-rc2

mmc: extend the slot-gpio card-detection to use host's .card_event() method

2012-12-07T18:55:50+00:00

The slot-gpio API provides a generic card-detection handler. To support a
wider range of hosts it has to call the host's card-event callback, if
implemented. Also increase the debounce interval to 200ms to match the
SDHCI driver.

Signed-off-by: Guennadi Liakhovetski 
Reviewed-by: Shawn Guo 
Signed-off-by: Chris Ball

mmc: Limit MMC speed to 52MHz if not HS200

2012-12-06T18:55:11+00:00

If "caps2" host capabilities does not indicate support for MMC
HS200, don't allow clock speeds >52MHz. Currently, for MMC, the
clock speed is set to the lesser of the max speed the eMMC module
supports (card->ext_csd.hs_max_dtr) or the max base clock of the
host controller (host->f_max based on BASE_CLK_FREQ in the host
CAPS register). This means that a host controller that doesn't
support HS200 mode but has a base clock of 100MHz and an eMMC module
that supports HS200 speeds will end up using a 100MHz clock.

Signed-off-by: Al Cooper 
Signed-off-by: Chris Ball

mmc: Remove redundant null check before kfree in bus.c

2012-12-06T18:55:07+00:00

kfree on a null pointer is a no-op.

Signed-off-by: Sachin Kamat 
Signed-off-by: Chris Ball

mmc: Remove redundant null check before kfree in sdio_bus.c

2012-12-06T18:55:06+00:00

kfree on a null pointer is a no-op.

Signed-off-by: Sachin Kamat 
Signed-off-by: Chris Ball

mmc: sdio: Add empty bus-level suspend/resume callbacks

2012-12-06T18:55:04+00:00

Suspend methods provided by SDIO drivers are not supposed to be called by
the PM core.  Instead, when the SDIO core gets to suspend a device's
ancestor, it calls the device driver's suspend routine.  However, the PM
core executes suspend callback routines directly for device drivers whose
bus types don't provide suspend callbacks.  In consequece, because the
SDIO bus type doesn't provide a suspend callback, the SDIO drivers'
suspend routines will be executed by the PM core (which shouldn't
happen).

To prevent this from happening, add empty system suspend/resume callbacks
for the SDIO bus type.

An analogous change had been made already by commit (e841a7c mmc: sdio:
Use empty system suspend/resume callbacks at the bus level), but then it
was reverted inadvertently by commit (d8e2ac3 mmc: sdio: Fix PM_SLEEP
related build warnings) that attempted to fix build warnings introduced
by commit e841a7c.

Reported-by: NeilBrown 
Signed-off-by: Rafael J. Wysocki 
Signed-off-by: Chris Ball

mmc: core: Add mmc_set_blockcount feature

2012-12-06T18:54:48+00:00

Provide support for automatically sending Set Block Count
(CMD23) messages. Used at least for RPMB support.

Signed-off-by: Alex Macro 
Signed-off-by: Loic Pallardy 
Reviewed-by: Namjae Jeon 
Acked-by: Linus Walleij 
Acked-by: Johan Rudholm 
Acked-by: Krishna Konda 
Signed-off-by: Chris Ball

mmc: core: Extend sysfs to ext_csd parameters for RPMB support

2012-12-06T18:54:48+00:00

Extend current sysfs access to ext_csd rpmb parameters (RPMB partition
size) and rel_sector information.

Signed-off-by: Loic Pallardy 
Reviewed-by: Namjae Jeon 
Acked-by: Linus Walleij 
Acked-by: Johan Rudholm 
Acked-by: Krishna Konda 
Signed-off-by: Chris Ball

mmc: core: Expose access to RPMB partition

2012-12-06T18:54:46+00:00

Following JEDEC standard, if the mmc supports RPMB partition,
a new interface is created and exposed via /dev/block.
Users will be able to access RPMB partition using standard
mmc IOCTL commands.

Signed-off-by: Alex Macro 
Signed-off-by: Loic Pallardy 
Reviewed-by: Namjae Jeon 
Acked-by: Linus Walleij 
Acked-by: Johan Rudholm 
Acked-by: Krishna Konda 
Signed-off-by: Chris Ball

mmc: Standardise capability type

2012-12-06T18:54:44+00:00

There are discrepancies with regards to how MMC capabilities
are carried throughout the subsystem. Let's standardise them
to eliminate any confusion.

Signed-off-by: Lee Jones 
Signed-off-by: Chris Ball

mmc: sdio: Use multiple scatter/gather list

2012-12-06T18:54:43+00:00

Before this patch, we always used only single sg entry for SDIO transfer.
This patch switches to using multiple sg entries. In the case of dwmci,
it supports only up to 4KB size per single sg entry. So if we want to
transfer more than 4KB, we should send more than 1 command.

When we tested before applying this patch, it took around 335 us for
5K(5120) bytes transfer with dwmci controller. After applying this patch,
it takes 242 us for 5K bytes. So this patch makes around 38% performance
improvement for 5K bytes transfer. If the transfer size is bigger, then
the performance improvement ratio will be increased.

Signed-off-by: Kyoungil Kim 
Signed-off-by: Chris Ball