diff options
| author |   Ulf Hansson <ulf.hansson@linaro.org> | 2014-12-01 16:13:39 +0100 |
|---|---|---|
| committer | Ulf Hansson <ulf.hansson@linaro.org> | 2015-01-19 09:56:23 +0100 |
| commit | 6c2c6506101f030808c0f2d429399dc1ee7a1a06 (patch) | |
| tree | 66de5463c6bd97152d3b31dea51b48c6a79bfff3 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | mmc: mmci: Do pm_runtime_put() after the host has been added (diff) | |
| download | wireguard-linux-6c2c6506101f030808c0f2d429399dc1ee7a1a06.tar.xz wireguard-linux-6c2c6506101f030808c0f2d429399dc1ee7a1a06.zip | |
mmc: dw_mmc: Convert to mmc_send_tuning()
Instead of having a local hack taking care of sending the tuning
command and as well to verify the response pattern, let's convert to
the common mmc_send_tuning() API.
This change affects the Exynos variant, since it's the only one which
support the dw_mmc's ->execute_tuning() callback.
It's seems like dw_mmc internal logic expects failed data transfers to
be ended using a stop command. Let the tuning requests also fall into
this category, since there are data transfer involved.
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Acked-by: Jaehoon Chung <jh80.chung@samsung.com>
Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
Tested-by: Alim Akhtar <alim.akhtar@samsung.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions