From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: linux-mmc@vger.kernel.org
Cc: cjb@laptop.org, Giuseppe Cavallaro <peppe.cavallaro@st.com>
Subject: [PATCH] mmc: sdhci: fix caps2 for HS200
Date: Tue, 11 Jun 2013 16:09:20 +0200 [thread overview]
Message-ID: <1370959760-27215-1-git-send-email-peppe.cavallaro@st.com> (raw)
Although the HC supports HS200 (eMMC) the caps2 are always zero; this means that
no way to use the super speed mode (when init the card).
If the HC support SDR104, for SD3.0, so it also supports HS200 for eMMC and
this patch just sets the MMC_CAP2_HS200 in the host caps2 field.
Reported-by: Youssef Triki <youssef.triki@st.com>
Signed-off-by: Giuseppe Cavallaro <peppe.cavallaro@st.com>
---
drivers/mmc/host/sdhci.c | 8 ++++++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
index 2ea429c..5626f5f 100644
--- a/drivers/mmc/host/sdhci.c
+++ b/drivers/mmc/host/sdhci.c
@@ -2962,9 +2962,13 @@ int sdhci_add_host(struct sdhci_host *host)
mmc->caps |= MMC_CAP_UHS_SDR12 | MMC_CAP_UHS_SDR25;
/* SDR104 supports also implies SDR50 support */
- if (caps[1] & SDHCI_SUPPORT_SDR104)
+ if (caps[1] & SDHCI_SUPPORT_SDR104) {
mmc->caps |= MMC_CAP_UHS_SDR104 | MMC_CAP_UHS_SDR50;
- else if (caps[1] & SDHCI_SUPPORT_SDR50)
+ /* SD3.0: SDR104 is supported so from eMMC caps2
+ * can be promoted to support HS200.
+ */
+ mmc->caps2 |= MMC_CAP2_HS200;
+ } else if (caps[1] & SDHCI_SUPPORT_SDR50)
mmc->caps |= MMC_CAP_UHS_SDR50;
if (caps[1] & SDHCI_SUPPORT_DDR50)
--
1.7.4.4
next reply other threads:[~2013-06-11 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 14:09 Giuseppe CAVALLARO [this message]
2013-06-11 15:09 ` [PATCH] mmc: sdhci: fix caps2 for HS200 Philip Rakity
2013-06-12 6:16 ` [PATCH (v2)] " Giuseppe CAVALLARO
2013-06-13 8:59 ` Philip Rakity
2013-06-18 2:32 ` Shen, Jackey
2013-06-20 8:56 ` Giuseppe CAVALLARO
2013-06-20 9:16 ` Youssef TRIKI
2013-06-22 8:33 ` Shen, Jackey
2013-06-23 7:52 ` Giuseppe CAVALLARO
2013-06-27 15:50 ` Chris Ball
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=1370959760-27215-1-git-send-email-peppe.cavallaro@st.com \
--to=peppe.cavallaro@st.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.