From: Wolfram Sang <w.sang@pengutronix.de>
To: joancarles <joancarles@fqingenieria.es>
Cc: "Eric Bénard" <eric@eukrea.com>,
"Zhu Richard-R65037" <r65037@freescale.com>,
shawn.guo@linaro.org, linux-mmc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [MX25][MMC] mmc esdhc failure in 3.3
Date: Tue, 27 Mar 2012 11:45:45 +0200 [thread overview]
Message-ID: <20120327094545.GE6790@pengutronix.de> (raw)
In-Reply-To: <7f2ae9e3800848e140461a0506808fb4@mail.fqingenieria.es>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
> Might be unrelated, however I have been keeping my eyes on the fix
> of ENGcm07207 quirk introduced with 16a790bcc. According to the
> IMX25CE.pdf, to abort data transfers on the AHB, software can reset
> the eSDHC by writing 1 to SYSCTL[24] (RSTA), which currently is not
> done with SDHCI_QUIRK_NO_MULTIBLOCK. It sets the max_blk_count to 1
> instead of 65535. Not sure if this is also limiting the speed.
Oh, it is limiting speed, for sure.
SDHCI_QUIRK_NO_MULTIBLOCK is a _generic_ quirk which can be enabled by
various buggy sdhci implementations, not only esdhc (which is pretty
good at being buggy). It is not there to fix MX25 specific issues,
that would have to be done seperately in sdhci-esdhc-imx.c.
So, the above quirk is a big hammer solution. There might be more
precise ones, but those still would have to be developed. I don't know
of anyone planning to do this.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-03-27 9:45 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
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 [this message]
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=20120327094545.GE6790@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=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 \
/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