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

workqueue: deprecate system_nrt[_freezable]_wq

2012-08-20T21:51:24+00:00

system_nrt[_freezable]_wq are now spurious.  Mark them deprecated and
convert all users to system[_freezable]_wq.

If you're cc'd and wondering what's going on: Now all workqueues are
non-reentrant, so there's no reason to use system_nrt[_freezable]_wq.
Please use system[_freezable]_wq instead.

This patch doesn't make any functional difference.

Signed-off-by: Tejun Heo 
Acked-By: Lai Jiangshan 

Cc: Jens Axboe 
Cc: David Airlie 
Cc: Jiri Kosina 
Cc: "David S. Miller" 
Cc: Rusty Russell 
Cc: "Paul E. McKenney" 
Cc: David Howells

mmc: prohibit card detection when host is not ready

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

Currently mmc host drivers have to decide whether to enable card
detection before calling mmc_add_host() -- in which case a card
insertion event can arrive before the host has been completely
initialised -- or after mmc_add_host(), in which case the initial
card detection can be problematic.

This patch adds an explicit indication of when card detection should
not be carried out. With it in place enabling card detection before
calling mmc_add_host() should be safe. Similarly, disabling it again
after calling mmc_remove_host() will avoid any races.

Signed-off-by: Guennadi Liakhovetski 
Signed-off-by: Chris Ball

mmc: core: convert slot functions to managed allocation

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

This prepares for the addition of further slot functions.

Signed-off-by: Guennadi Liakhovetski 
Signed-off-by: Chris Ball

mmc: core: use a more generic name for slot function types and fields

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

struct mmc_host::hotplug is becoming a generic hook for slot functions.
Rename it accordingly.

Signed-off-by: Guennadi Liakhovetski 
Signed-off-by: Chris Ball

mmc: start removing enable / disable API

2012-03-27T16:20:03+00:00

Most parts of the enable / disable API are no longer used and
can be removed.

Signed-off-by: Adrian Hunter 
Tested-by: Venkatraman S 
Tested-by: Jaehoon Chung 
Signed-off-by: Chris Ball

mmc: core: fix regression: set default clock gating delay to 0

2012-03-04T17:18:40+00:00

A recent commit "mmc: core: Use delayed work in clock gating framework"
(597dd9d79cfbbb1) introduced a default 200ms delay before clock gating
actually takes place.  This means that every time an MMC interface
becomes idle it first stays on for 200ms before gating its clock. This
leads to increased power consumption and is therefore a clear regression.
This patch restores the original behaviour by setting the default delay
to 0. Users prioritising throughput over power efficiency can still
modify the delay via sysfs.

Signed-off-by: Guennadi Liakhovetski 
Signed-off-by: Chris Ball

mmc: core: Fixup delayed work clock gating patch

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

c31b50e (mmc: core: Use delayed work in clock gating framework,
2011-11-14) missed a few things during review:

 o A useless pr_info()

 o milliseconds was written as two words

 o The sysfs file had units in its output

Fix all three problems.

Signed-off-by: Stephen Boyd 
Cc: Sujit Reddy Thumma 
Signed-off-by: Chris Ball

mmc: core: Use delayed work in clock gating framework

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

Current clock gating framework disables the MCI clock as soon as the
request is completed and enables it when a request arrives. This aggressive
clock gating framework, when enabled, cause following issues:

When there are back-to-back requests from the Queue layer, we unnecessarily
end up disabling and enabling the clocks between these requests since 8MCLK
clock cycles is a very short duration compared to the time delay between
back to back requests reaching the MMC layer. This overhead can effect the
overall performance depending on how long the clock enable and disable
calls take which is platform dependent. For example on some platforms we
can have clock control not on the local processor, but on a different
subsystem and the time taken to perform the clock enable/disable can add
significant overhead.

Also if the host controller driver decides to disable the host clock too
when mmc_set_ios function is called with ios.clock=0, it adds additional
delay and it is highly possible that the next request had already arrived
and unnecessarily blocked in enabling the clocks. This is seen frequently
when the processor is executing at high speeds and in multi-core platforms
thus reduces the overall throughput compared to if clock gating is
disabled.

Fix this by delaying turning off the clocks by posting request on
delayed workqueue. Also cancel the unscheduled pending work, if any,
when there is access to card.

sysfs entry is provided to tune the delay as needed, default
value set to 200ms.

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

Revert "mmc: enable runtime PM by default"

2011-12-19T23:51:38+00:00

When SDIO runtime PM was originally introduced, we immediately faced
two regressions with two different chipsets, and in response decided
not to enable it by default.

With the recent work on the 8686 we hoped we found all the gotchas,
so 08da834 did make sense (at least experimentally).

Unfortunately we now see that some setups out there still refuse to
work when SDIO runtime PM is enabled by default (see
http://www.spinics.net/lists/linux-mmc/msg11161.html), and obviously
we can't live with these kind of regressions.

This reverts commit 08da834a24312157f512224691ad1fddd11c1073.

Signed-off-by: Ohad Ben-Cohen 
Cc: Daniel Drake 
Signed-off-by: Chris Ball

mmc: Add export.h for EXPORT_SYMBOL/THIS_MODULE as required

2011-10-31T23:32:06+00:00

These two basic defines were everywhere, simply because module.h
was also everywhere.   But we are cleaning up the latter.  So make
the exporters actually call out their need for the include.

Signed-off-by: Paul Gortmaker