Commit 07b24041 authored by Doug Anderson's avatar Doug Anderson Committed by Chris Ball

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: default avatarDoug Anderson <dianders@chromium.org>
Acked-by: default avatarSeungwon Jeon <tgih.jun@samsung.com>
Acked-by: default avatarOlof Johansson <olof@lixom.net>
Signed-off-by: default avatarChris Ball <cjb@laptop.org>
parent 488755b5
...@@ -175,16 +175,6 @@ static int dw_mci_exynos_setup_bus(struct dw_mci *host, ...@@ -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) if (host->pdata->quirks & DW_MCI_QUIRK_BROKEN_CARD_DETECTION)
return 0; return 0;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment