[RFC PATCH 1/3] mmc: omap_hsmmc: set host capabilities by reading MMCHS_CAPA2 register
From: Kishon Vijay Abraham I
Date: Thu Nov 13 2014 - 09:54:39 EST
From: Viswanath Puttagunta <vishp@xxxxxx>
set SDR104, SDR50, DDR50 and HS200 capability flags to caps/caps2 by reading
MMCHS_CAPA2 register.
Signed-off-by: Viswanath Puttagunta <vishp@xxxxxx>
Signed-off-by: Sourav Poddar <sourav.poddar@xxxxxx>
Signed-off-by: Kishon Vijay Abraham I <kishon@xxxxxx>
Suggested-by: Misael Lopez Cruz <misael.lopez@xxxxxx>
---
drivers/mmc/host/omap_hsmmc.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
index df27bb4..2e42ed3 100644
--- a/drivers/mmc/host/omap_hsmmc.c
+++ b/drivers/mmc/host/omap_hsmmc.c
@@ -64,6 +64,7 @@
#define OMAP_HSMMC_ISE 0x0138
#define OMAP_HSMMC_AC12 0x013C
#define OMAP_HSMMC_CAPA 0x0140
+#define OMAP_HSMMC_CAPA2 0x0144
#define VS18 (1 << 26)
#define VS30 (1 << 25)
@@ -139,6 +140,10 @@
#define ACTO (1 << 1)
#define ACNE (1 << 0)
+#define SDR50 (1 << 0)
+#define SDR104 (1 << 1)
+#define DDR50 (1 << 2)
+
#define MMC_AUTOSUSPEND_DELAY 100
#define MMC_TIMEOUT_MS 20 /* 20 mSec */
#define MMC_TIMEOUT_US 20000 /* 20000 micro Sec */
@@ -2028,6 +2033,7 @@ static int omap_hsmmc_probe(struct platform_device *pdev)
unsigned tx_req, rx_req;
const struct omap_mmc_of_data *data;
void __iomem *base;
+ u32 reg;
match = of_match_device(of_match_ptr(omap_mmc_of_match), &pdev->dev);
if (match) {
@@ -2153,6 +2159,19 @@ static int omap_hsmmc_probe(struct platform_device *pdev)
mmc->pm_caps = mmc_slot(host).pm_caps;
+ reg = OMAP_HSMMC_READ(host->base, OMAP_HSMMC_CAPA2);
+
+ if (reg & SDR50)
+ mmc->caps |= MMC_CAP_UHS_DDR50;
+
+ if (reg & SDR104) {
+ mmc->caps |= MMC_CAP_UHS_SDR104;
+ mmc->caps2 |= MMC_CAP2_HS200;
+ }
+
+ if (reg & DDR50)
+ mmc->caps |= MMC_CAP_UHS_DDR50;
+
omap_hsmmc_conf_bus_power(host);
if (!pdev->dev.of_node) {
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/