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 2/2] mmc: tmio: remove obsolete PM workaround
Date: Wed, 31 Jul 2019 18:17:37 +0200 [thread overview]
Message-ID: <1564589857-17720-3-git-send-email-uli+renesas@fpond.eu> (raw)
In-Reply-To: <1564589857-17720-1-git-send-email-uli+renesas@fpond.eu>
Obsoleted by commit 7ff213193310ef8d ("mmc: tmio: move runtime PM
enablement to the driver implementations").
Signed-off-by: Ulrich Hecht <uli+renesas@fpond.eu>
---
drivers/mmc/host/tmio_mmc_core.c | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/drivers/mmc/host/tmio_mmc_core.c b/drivers/mmc/host/tmio_mmc_core.c
index 733ff96..72877c6 100644
--- a/drivers/mmc/host/tmio_mmc_core.c
+++ b/drivers/mmc/host/tmio_mmc_core.c
@@ -1221,15 +1221,6 @@ int tmio_mmc_host_probe(struct tmio_mmc_host *_host)
_host->reset = tmio_mmc_reset;
/*
- * On Gen2+, eMMC with NONREMOVABLE currently fails because native
- * hotplug gets disabled. It seems RuntimePM related yet we need further
- * research. Since we are planning a PM overhaul anyway, let's enforce
- * for now the device being active by enabling native hotplug always.
- */
- if (pdata->flags & TMIO_MMC_MIN_RCAR2)
- _host->native_hotplug = true;
-
- /*
* While using internal tmio hardware logic for card detection, we need
* to ensure it stays powered for it to work.
*/
--
2.7.4
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 ` [PATCH v2 1/2] mmc: tmio: leave clock handling to runtime PM if enabled Ulrich Hecht
2019-08-02 13:24 ` 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 ` Ulrich Hecht [this message]
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-3-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).