From: "Eric Bénard" <eric@eukrea.com>
To: joancarles <joancarles@fqingenieria.es>
Cc: Zhu Richard-R65037 <r65037@freescale.com>,
shawn.guo@linaro.org, linux-mmc@vger.kernel.org,
Wolfram Sang <w.sang@pengutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [MX25][MMC] mmc esdhc failure in 3.3
Date: Tue, 27 Mar 2012 10:12:59 +0200 [thread overview]
Message-ID: <20120327101259.73525f9d@eb-e6520> (raw)
In-Reply-To: <85b807b77d73328485781d6fa1568e46@mail.fqingenieria.es>
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
Hi,
Le Tue, 27 Mar 2012 09:32:36 +0200,
joancarles <joancarles@fqingenieria.es> a écrit :
> G'day
>
> This is still present, and we have absolutely no idea where to continue
> searching for the solution of the problem. Any pointers? Any git trees
> of mmc driver changes we could try? Anybody else with a MX25 that has
> this issue?
>
does that attached patch fix your problem ?
Eric
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-esdhc-imx-unbreak-on-i.MX25.patch --]
[-- Type: text/x-patch, Size: 1084 bytes --]
From 6b41fd664bdb4755a0c22abdbe5524a76ac74330 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Eric=20B=C3=A9nard?= <eric@eukrea.com>
Date: Mon, 12 Mar 2012 22:17:05 +0100
Subject: [PATCH] esdhc-imx: unbreak on i.MX25
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Signed-off-by: Eric Bénard <eric@eukrea.com>
---
drivers/mmc/host/sdhci-esdhc-imx.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc/host/sdhci-esdhc-imx.c b/drivers/mmc/host/sdhci-esdhc-imx.c
index 4dc0028..fe0da1c 100644
--- a/drivers/mmc/host/sdhci-esdhc-imx.c
+++ b/drivers/mmc/host/sdhci-esdhc-imx.c
@@ -400,8 +400,7 @@ static int __devinit sdhci_esdhc_imx_probe(struct platform_device *pdev)
clk_enable(clk);
pltfm_host->clk = clk;
- if (!is_imx25_esdhc(imx_data))
- host->quirks |= SDHCI_QUIRK_BROKEN_TIMEOUT_VAL;
+ host->quirks |= SDHCI_QUIRK_BROKEN_TIMEOUT_VAL;
if (is_imx25_esdhc(imx_data) || is_imx35_esdhc(imx_data))
/* Fix errata ENGcm07207 present on i.MX25 and i.MX35 */
--
1.7.7.6
next prev parent reply other threads:[~2012-03-27 8:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 11:29 [MX25][MMC] mmc esdhc failure in 3.3-rc5 joancarles
2012-03-12 13:12 ` [MX25][MMC] mmc esdhc failure in 3.3-rc5 (still present in rc7) joancarles
2012-03-12 13:24 ` [MX25][MMC] mmc esdhc failure in 3.3-rc5 Wolfram Sang
2012-03-12 14:50 ` joancarles
2012-03-12 21:45 ` Wolfram Sang
2012-03-13 11:20 ` joancarles
2012-03-13 5:55 ` Zhu Richard-R65037
2012-03-16 15:03 ` joancarles
2012-03-27 7:32 ` [MX25][MMC] mmc esdhc failure in 3.3 joancarles
2012-03-27 7:59 ` joancarles
2012-03-27 8:12 ` Eric Bénard [this message]
2012-03-27 8:46 ` joancarles
2012-03-27 8:58 ` Eric Bénard
2012-03-27 13:03 ` Zhu Richard-R65037
2012-03-27 9:01 ` Wolfram Sang
2012-03-27 9:06 ` Eric Bénard
2012-03-27 9:14 ` Wolfram Sang
2012-03-27 9:23 ` Eric Bénard
2012-03-27 9:36 ` Wolfram Sang
2012-03-27 9:33 ` joancarles
2012-03-27 9:40 ` Eric Bénard
2012-03-27 10:56 ` joancarles
2012-03-28 9:26 ` joancarles
2012-03-28 14:01 ` joancarles
2012-03-27 9:45 ` Wolfram Sang
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=20120327101259.73525f9d@eb-e6520 \
--to=eric@eukrea.com \
--cc=joancarles@fqingenieria.es \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=r65037@freescale.com \
--cc=shawn.guo@linaro.org \
--cc=w.sang@pengutronix.de \
/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