linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eric@eukrea.com (Eric Bénard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] mmc: quirk fix for timeout problem
Date: Thu, 21 Oct 2010 22:28:49 +0200	[thread overview]
Message-ID: <4CC0A281.1010202@eukrea.com> (raw)
In-Reply-To: <AANLkTikokkVaAjA+b6f56Syv0h8odiN4koJTOaFW_Ebx@mail.gmail.com>

Hi,

test protocol : booting a 2.6.36-rc8 kernel with a rootfs (ext3 formated, 
generated with OpenEmbedded for armv5, loading and launching qtdemo 4.6.3) on 
a 8GB ?SDHC  (uSD reformated after each board tests to trigger lot of 
read/writes on the first init).

* on an i.MX357 (rev 2.1) without this patch leads to :
mmcblk0: error -110 transferring data, sector 7347024, nr 8, card status 0xe00
end_request: I/O error, dev mmcblk0, sector 7347025

Same card, same board, with the timeout quirk patch : boots fine without any 
error.

Reverted the patch: timeout errors came back.

==> quirk timeout patch needed for the i.MX35

* on an i.MX257 (tested twice) :
Same kernel tree, same rootfs, same motherboard, same uSD, only the CPU module 
change : no error without the patch (and no error with the patch also ;-).

==> quirk timeout patch not needed for the i.MX25

* on an i.MX515 :
Same kernel tree, same rootfs, same motherboard, same uSD (re-formated), only 
the CPU module change without this patch leads to :
mmcblk0: error -84 transferring data, sector 1315598, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1315598

Same card, same board, with the timeout quirk patch : boots fine without any 
error.

Reverted the patch: timeout errors came back.

==> quirk timeout patch needed for the i.MX51

Updated patch follows.

Eric

  reply	other threads:[~2010-10-21 20:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20  8:53 [PATCH 0/2] babbage: support mmc device Shawn Guo
2010-10-20  9:22 ` [PATCH 1/2] mmc: quirk fix for timeout problem Shawn Guo
2010-10-20 11:27   ` Wolfram Sang
2010-10-21 16:11     ` Shawn Guo
2010-10-21 16:43       ` Wolfram Sang
2010-10-21 17:10       ` Nicolas Pitre
2010-10-21 18:14         ` Shawn Guo
2010-10-21 20:28           ` Eric Bénard [this message]
2010-10-21 21:20             ` [PATCH 1/2] sdhci-esdhc-imx: fix timeout on i.MX's sdhci Eric Bénard
2010-10-22  6:15               ` Wolfram Sang
2010-10-22 23:12               ` Chris Ball
2010-10-22 23:57                 ` Eric Bénard
2010-11-07 22:51                   ` Chris Ball
2010-10-22 23:57                 ` [PATCH 2/2] sdhci-esdhc-imx: enable QUIRK_NO_MULTIBLOCK only for i.MX25 and i.MX35 Eric Bénard
2010-10-21 21:20             ` Eric Bénard
2010-10-22  6:18               ` Wolfram Sang
2010-10-22  7:07                 ` Eric Bénard
2010-10-22  8:46                 ` [PATCH v2 1/2] sdhci-esdhc-imx: fix timeout on i.MX's sdhci Eric Bénard
2010-10-22  8:46                 ` [PATCH v2 2/2] sdhci-esdhc-imx: enable QUIRK_NO_MULTIBLOCK only for i.MX25 and i.MX35 Eric Bénard
2010-10-22 10:54                   ` Wolfram Sang
2010-10-22  4:39             ` [PATCH 1/2] mmc: quirk fix for timeout problem Shawn Guo
2010-10-20  9:24 ` [PATCH 2/2] babbage: esdhc device registration Shawn Guo
2010-10-20 11:30   ` Wolfram Sang
2010-10-20 11:52   ` Amit Kucheria

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=4CC0A281.1010202@eukrea.com \
    --to=eric@eukrea.com \
    --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).