From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kernel@avr32linux.org, Hein_Tibosch <hein_tibosch@yahoo.es>,
linux-kernel@vger.kernel.org,
Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Subject: Re: [PATCH] atmel-mci: Initialize BLKR before sending data transfer command
Date: Mon, 6 Oct 2008 19:44:59 +0200 [thread overview]
Message-ID: <20081006194459.74ba0c84@mjolnir.drzeus.cx> (raw)
In-Reply-To: <1223046458-10851-1-git-send-email-haavard.skinnemoen@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 2620 bytes --]
Linus, any chance of getting this into .27? It has been seen in the
wild and causes I/O errors (which can lead to data loss).
If so, you can add:
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
On Fri, 3 Oct 2008 17:07:38 +0200
Haavard Skinnemoen <haavard.skinnemoen@atmel.com> wrote:
> The atmel-mci driver sometimes fails data transfers like this:
>
> mmcblk0: error -5 transferring data
> end_request: I/O error, dev mmcblk0, sector 2749769
> end_request: I/O error, dev mmcblk0, sector 2749777
>
> It turns out that this might be caused by the BLKR register (which
> contains the block size and the number of blocks being transfered) being
> initialized too late. This patch moves the initialization of BLKR so
> that it contains the correct value before the block transfer command is
> sent.
>
> This error is difficult to reproduce, but if you insert a long delay
> (mdelay(10) or thereabouts) between the calls to atmci_start_command()
> and atmci_submit_data(), all transfers seem to fail without this patch,
> while I haven't seen any failures with this patch.
>
> Reported-by: Hein_Tibosch <hein_tibosch@yahoo.es>
> Signed-off-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
> ---
> drivers/mmc/host/atmel-mci.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mmc/host/atmel-mci.c b/drivers/mmc/host/atmel-mci.c
> index 917035e..0000896 100644
> --- a/drivers/mmc/host/atmel-mci.c
> +++ b/drivers/mmc/host/atmel-mci.c
> @@ -426,8 +426,6 @@ static u32 atmci_submit_data(struct mmc_host *mmc, struct mmc_data *data)
> host->sg = NULL;
> host->data = data;
>
> - mci_writel(host, BLKR, MCI_BCNT(data->blocks)
> - | MCI_BLKLEN(data->blksz));
> dev_vdbg(&mmc->class_dev, "BLKR=0x%08x\n",
> MCI_BCNT(data->blocks) | MCI_BLKLEN(data->blksz));
>
> @@ -483,6 +481,10 @@ static void atmci_request(struct mmc_host *mmc, struct mmc_request *mrq)
> if (data->blocks > 1 && data->blksz & 3)
> goto fail;
> atmci_set_timeout(host, data);
> +
> + /* Must set block count/size before sending command */
> + mci_writel(host, BLKR, MCI_BCNT(data->blocks)
> + | MCI_BLKLEN(data->blksz));
> }
>
> iflags = MCI_CMDRDY;
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
rdesktop, core developer http://www.rdesktop.org
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-06 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 15:07 Haavard Skinnemoen
2008-10-06 17:44 ` Pierre Ossman [this message]
2008-10-06 17:51 ` Linus Torvalds
2008-10-06 18:09 ` Pierre Ossman
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=20081006194459.74ba0c84@mjolnir.drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=haavard.skinnemoen@atmel.com \
--cc=hein_tibosch@yahoo.es \
--cc=kernel@avr32linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®