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 <dianders@chromium.org>
Acked-by: Seungwon Jeon <tgih.jun@samsung.com>
Acked-by: Olof Johansson <olof@lixom.net>
Signed-off-by: Chris Ball <cjb@laptop.org>

diff --git a/drivers/mmc/host/dw_mmc-exynos.c b/drivers/mmc/host/dw_mmc-exynos.c
index 4d50da618166e33c03856fe5845e780d785ece46..72fd0f2c901312d1f98474ad4b4f016cf5f5cf39 100644 (file)
--- 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;