From: Ulrich Hecht <uli+renesas@fpond.eu>
To: linux-renesas-soc@vger.kernel.org, linux-mmc@vger.kernel.org
Cc: niklas.soderlund@ragnatech.se, wsa@the-dreams.de,
yamada.masahiro@socionext.com, geert@linux-m68k.org,
ulf.hansson@linaro.org, magnus.damm@gmail.com,
Ulrich Hecht <uli+renesas@fpond.eu>
Subject: [PATCH v2 1/2] mmc: tmio: leave clock handling to runtime PM if enabled
Date: Wed, 31 Jul 2019 18:17:36 +0200 [thread overview]
Message-ID: <1564589857-17720-2-git-send-email-uli+renesas@fpond.eu> (raw)
In-Reply-To: <1564589857-17720-1-git-send-email-uli+renesas@fpond.eu>
This fixes a clock imbalance that occurs on Renesas systems because the SD
clock is handled by both runtime PM and the hardware driver. After a
suspend/resume cycle both enable the same clock, resulting in an enable
count of 2 even if the clock is only used by one device.
See https://www.spinics.net/lists/linux-mmc/msg44431.html for details.
This patch removes the clock handling from the driver's runtime PM
callbacks and turns the clock off after probing if the device has a power
domain attached.
Reported-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Ulrich Hecht <uli+renesas@fpond.eu>
Tested-by: Niklas Söderlund <niklas.soderlund@ragnatech.se>
---
drivers/mmc/host/tmio_mmc_core.c | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/drivers/mmc/host/tmio_mmc_core.c b/drivers/mmc/host/tmio_mmc_core.c
index 31ffcc3..733ff96 100644
--- a/drivers/mmc/host/tmio_mmc_core.c
+++ b/drivers/mmc/host/tmio_mmc_core.c
@@ -1260,9 +1260,14 @@ int tmio_mmc_host_probe(struct tmio_mmc_host *_host)
/* See if we also get DMA */
tmio_mmc_request_dma(_host, pdata);
- pm_runtime_set_active(&pdev->dev);
+#ifdef CONFIG_PM
+ /* PM handles the clock; disable it so it won't be enabled twice. */
+ if (_host->clk_disable && pdev->dev.pm_domain)
+ _host->clk_disable(_host);
+ pm_runtime_get_sync(&pdev->dev);
pm_runtime_set_autosuspend_delay(&pdev->dev, 50);
pm_runtime_use_autosuspend(&pdev->dev);
+#endif
ret = mmc_add_host(mmc);
if (ret)
@@ -1325,7 +1330,8 @@ int tmio_mmc_host_runtime_suspend(struct device *dev)
if (host->clk_cache)
host->set_clock(host, 0);
- tmio_mmc_clk_disable(host);
+ if (!dev->pm_domain)
+ tmio_mmc_clk_disable(host);
return 0;
}
@@ -1340,7 +1346,9 @@ int tmio_mmc_host_runtime_resume(struct device *dev)
{
struct tmio_mmc_host *host = dev_get_drvdata(dev);
- tmio_mmc_clk_enable(host);
+ if (!dev->pm_domain)
+ tmio_mmc_clk_enable(host);
+
tmio_mmc_hw_reset(host->mmc);
if (host->clk_cache)
--
2.7.4
next prev parent reply other threads:[~2019-07-31 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 16:17 [PATCH v2 0/2] mmc: tmio: remove Gen2+ workaround and fix up Ulrich Hecht
2019-07-31 16:17 ` Ulrich Hecht [this message]
2019-08-02 13:24 ` [PATCH v2 1/2] mmc: tmio: leave clock handling to runtime PM if enabled Ulf Hansson
2019-08-22 6:35 ` Wolfram Sang
2019-08-22 9:43 ` Ulf Hansson
2019-08-22 9:52 ` Wolfram Sang
2019-07-31 16:17 ` [PATCH v2 2/2] mmc: tmio: remove obsolete PM workaround Ulrich Hecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1564589857-17720-2-git-send-email-uli+renesas@fpond.eu \
--to=uli+renesas@fpond.eu \
--cc=geert@linux-m68k.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=niklas.soderlund@ragnatech.se \
--cc=ulf.hansson@linaro.org \
--cc=wsa@the-dreams.de \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).