From: Doug Anderson Date: Fri, 11 Jan 2013 17:03:52 +0000 (+0000) Subject: mmc: dw_mmc: exynos: Remove code for wp-gpios X-Git-Tag: v3.9-rc1~78^2~52 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=07b240411f1e7528ed36e09979f40ccf4b844c8c;p=profile%2Fcommon%2Fkernel-common.git mmc: dw_mmc: exynos: Remove code for wp-gpios The exynos code claimed the write protect with devm_gpio_request() but never did anything with it. That meant that anyone using a write protect GPIO would effectively be write protected all the time. The handling for wp-gpios belongs in the main dw_mmc driver and has been moved there. Signed-off-by: Doug Anderson Acked-by: Seungwon Jeon Acked-by: Olof Johansson Signed-off-by: Chris Ball --- diff --git a/drivers/mmc/host/dw_mmc-exynos.c b/drivers/mmc/host/dw_mmc-exynos.c index 4d50da6..72fd0f2 100644 --- a/drivers/mmc/host/dw_mmc-exynos.c +++ b/drivers/mmc/host/dw_mmc-exynos.c @@ -175,16 +175,6 @@ static int dw_mci_exynos_setup_bus(struct dw_mci *host, } } - gpio = of_get_named_gpio(slot_np, "wp-gpios", 0); - if (gpio_is_valid(gpio)) { - if (devm_gpio_request(host->dev, gpio, "dw-mci-wp")) - dev_info(host->dev, "gpio [%d] request failed\n", - gpio); - } else { - dev_info(host->dev, "wp gpio not available"); - host->pdata->quirks |= DW_MCI_QUIRK_NO_WRITE_PROTECT; - } - if (host->pdata->quirks & DW_MCI_QUIRK_BROKEN_CARD_DETECTION) return 0;