From: Steffen Trumtrar <s.trumtrar@pengutronix.de>
To: linux-mmc@vger.kernel.org
Cc: Chris Ball <cjb@laptop.org>
Subject: Re: [BUG/RFC] SDHCI_QUIRK_NO_MULTIBLOCK for i.MX35/25
Date: Mon, 2 Dec 2013 09:58:06 +0100 [thread overview]
Message-ID: <20131202085806.GF25308@pengutronix.de> (raw)
In-Reply-To: <20131115091537.GF28658@pengutronix.de>
On Fri, Nov 15, 2013 at 10:15:37AM +0100, Steffen Trumtrar wrote:
> Hi!
>
>
> 1 Actual Use-Case
> =================
>
> I have a SDIO card with a Marvell 8787, that works fine on an i.MX53
> with the drivers/net/wireless/mwifiex/sdio.c driver. On an i.MX35
> however the loading of the firmware errors out on the very first
> single-block transfer with 1024 bytes payload.
>
>
> 2 Reason for failure
> ====================
>
> sdhci defines SDHCI_QUIRK_NO_MULTIBLOCK to completely disable
> multi-block transfers for a host. The max_blk_count is simply set to 1
> to achieve this. Currently only i.MX35 and i.MX25 seem to be the only
> users of that quirk. The quirk is used to fix an errata on these
> SoCs, that says, that "CMD12 abort operation does not abort data
> transfer on AHB". (ENGcm07207)
>
> So, this is a problem regarding only SD and not SDIO. On this special
> SDIO card, it looks like multi-block transfer has to be used for
> anything >16 bytes. Removing the quirk fixes the firmware loading
> error. The device is detected successfully after loading and can
> connect to an AP.
>
>
> 3 Question
> ==========
>
> And here comes the question: What would be the correct approach to fix
> that and differentiate those two cases, so that we can use multi-block
> transfers with CMD53 but not with CMD25(?!) ?
>
> 1a. As I see no other users of that quirk, it might be okay to rename
> it, to better reflect the actual problem it fixes (broken CMD12 or
> something).
>
> 1b. When the host knows with what it deals with (SDIO or SD) set the
> max_blk_count according to the quirk. And only in the SD case, that is.
>
> or
>
> 2. Introduce a max_blk_count_sd and max_blk_count_sdio and use them
> everywhere. Seems rather invasive and over the top.
>
> or
>
> 3. something better.
>
>
Ping...
Regards,
Steffen
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2013-12-02 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 9:15 [BUG/RFC] SDHCI_QUIRK_NO_MULTIBLOCK for i.MX35/25 Steffen Trumtrar
2013-12-02 8:58 ` Steffen Trumtrar [this message]
2013-12-17 9:28 ` Steffen Trumtrar
2013-12-17 11:43 ` Dong Aisheng
2014-01-20 10:33 ` Steffen Trumtrar
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=20131202085806.GF25308@pengutronix.de \
--to=s.trumtrar@pengutronix.de \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.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).