From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] ARM: dts: imx51-babbage: Fix esdhc setup
Date: Sun, 1 Jun 2014 23:22:19 +0800 [thread overview]
Message-ID: <20140601152216.GD11061@dragon> (raw)
In-Reply-To: <1400848384-3226-6-git-send-email-s.hauer@pengutronix.de>
On Fri, May 23, 2014 at 02:33:04PM +0200, Sascha Hauer wrote:
> - Move cd/wp pinctrl from the hog group to the esdhc groups
> - use gpio for card detection / write protection on esdhc2 since
> the controller based detection does not work
I tracked it a little bit and found that the controller based detection
works fine with v3.13 and starts being broken from v3.14-rc1. The
offending commit seems to be 89d7e5c13122 (mmc: sdhci-esdhc-imx: add
runtime pm support).
I will probably apply the patch as it is anyway. But I'm wondering if
we should fix the regression and keep maintaining the support of
controller based cd/wp in sdhci-esdhc-imx driver.
Shawn
> - Fix cd gpio polarity for esdhc1. This is wrong and currently
> only works because the imx esdhc driver ignores the polarity.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
> arch/arm/boot/dts/imx51-babbage.dts | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/arch/arm/boot/dts/imx51-babbage.dts b/arch/arm/boot/dts/imx51-babbage.dts
> index 9e9deb2..28d4553 100644
> --- a/arch/arm/boot/dts/imx51-babbage.dts
> +++ b/arch/arm/boot/dts/imx51-babbage.dts
> @@ -134,15 +134,15 @@
> &esdhc1 {
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_esdhc1>;
> - fsl,cd-controller;
> - fsl,wp-controller;
> + cd-gpios = <&gpio1 0 GPIO_ACTIVE_LOW>;
> + wp-gpios = <&gpio1 1 GPIO_ACTIVE_HIGH>;
> status = "okay";
> };
>
> &esdhc2 {
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_esdhc2>;
> - cd-gpios = <&gpio1 6 GPIO_ACTIVE_HIGH>;
> + cd-gpios = <&gpio1 6 GPIO_ACTIVE_LOW>;
> wp-gpios = <&gpio1 5 GPIO_ACTIVE_HIGH>;
> status = "okay";
> };
> @@ -300,10 +300,6 @@
> imx51-babbage {
> pinctrl_hog: hoggrp {
> fsl,pins = <
> - MX51_PAD_GPIO1_0__SD1_CD 0x20d5
> - MX51_PAD_GPIO1_1__SD1_WP 0x20d5
> - MX51_PAD_GPIO1_5__GPIO1_5 0x100
> - MX51_PAD_GPIO1_6__GPIO1_6 0x100
> MX51_PAD_EIM_A27__GPIO2_21 0x5
> MX51_PAD_CSPI1_SS0__GPIO4_24 0x85
> MX51_PAD_CSPI1_SS1__GPIO4_25 0x85
> @@ -330,6 +326,8 @@
>
> pinctrl_esdhc1: esdhc1grp {
> fsl,pins = <
> + MX51_PAD_GPIO1_0__GPIO1_0 0x20d5
> + MX51_PAD_GPIO1_1__GPIO1_1 0x20d5
> MX51_PAD_SD1_CMD__SD1_CMD 0x400020d5
> MX51_PAD_SD1_CLK__SD1_CLK 0x20d5
> MX51_PAD_SD1_DATA0__SD1_DATA0 0x20d5
> @@ -341,6 +339,8 @@
>
> pinctrl_esdhc2: esdhc2grp {
> fsl,pins = <
> + MX51_PAD_GPIO1_5__GPIO1_5 0x100
> + MX51_PAD_GPIO1_6__GPIO1_6 0x100
> MX51_PAD_SD2_CMD__SD2_CMD 0x400020d5
> MX51_PAD_SD2_CLK__SD2_CLK 0x20d5
> MX51_PAD_SD2_DATA0__SD2_DATA0 0x20d5
> --
> 2.0.0.rc0
>
next prev parent reply other threads:[~2014-06-01 15:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 12:32 [PATCH] MMC: use mmc_of_parse in sdhci-esdhc-imx Sascha Hauer
2014-05-23 12:33 ` [PATCH 1/5] mmc: sdhci-esdhc-imx: add f_max field to private data Sascha Hauer
2014-06-01 7:45 ` Shawn Guo
2014-06-02 6:40 ` Sascha Hauer
2014-05-23 12:33 ` [PATCH 2/5] mmc: sdhci-esdhc-imx: introduce function for parsing platform_data Sascha Hauer
2014-05-23 12:33 ` [PATCH 3/5] mmc: sdhci-esdhc-imx: straighten SDHCI_QUIRK_BROKEN_CARD_DETECTION flag Sascha Hauer
2014-05-23 12:33 ` [PATCH 4/5] mmc: sdhci-esdhc-imx: use mmc_of_parse Sascha Hauer
2014-05-23 12:33 ` [PATCH 5/5] ARM: dts: imx51-babbage: Fix esdhc setup Sascha Hauer
2014-06-01 15:22 ` Shawn Guo [this message]
2014-06-05 10:39 ` Sascha Hauer
2014-06-09 3:38 ` Shawn Guo
2014-06-09 3:41 ` Shawn Guo
2014-06-10 8:01 ` Lothar Waßmann
2014-06-21 7:56 ` Shawn Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140601152216.GD11061@dragon \
--to=shawn.guo@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).