Before adjusting this patch, always return 0.
Then clock-setup would be always succeed.
In dw-mmc.c, it's checked like below
ret = drv_data->setup_clock(host);
if (ret) {
...
Never entered at here..
}
Signed-off-by: Jaehoon Chung <[email protected]>
Signed-off-by: Kyungmin Park <[email protected]>
---
drivers/mmc/host/dw_mmc-exynos.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mmc/host/dw_mmc-exynos.c b/drivers/mmc/host/dw_mmc-exynos.c
index 72fd0f2..764ff29 100644
--- a/drivers/mmc/host/dw_mmc-exynos.c
+++ b/drivers/mmc/host/dw_mmc-exynos.c
@@ -99,7 +99,7 @@ static int dw_mci_exynos_setup_clock(struct dw_mci *host)
else if (priv->ctrl_type == DW_MCI_TYPE_EXYNOS4210)
host->bus_hz /= EXYNOS4210_FIXED_CIU_CLK_DIV;
- return 0;
+ return host->bus_hz ? 0 : -EINVAL;
}
static void dw_mci_exynos_prepare_command(struct dw_mci *host, u32 *cmdr)
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
