From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: ludovic.desroches@atmel.com, linux-mmc@vger.kernel.org, cjb@laptop.org
Cc: linux-arm-kernel@lists.infradead.org, etesial@gmail.com
Subject: Re: [PATCH] mmc: atmel-mci: abort transfer on timeout error
Date: Tue, 10 Sep 2013 09:54:39 +0200 [thread overview]
Message-ID: <522ED03F.5070404@atmel.com> (raw)
In-Reply-To: <1378740596-25026-1-git-send-email-ludovic.desroches@atmel.com>
On 09/09/2013 17:29, ludovic.desroches@atmel.com :
> From: Ludovic Desroches <ludovic.desroches@atmel.com>
>
> When a software timeout occurs, the transfer is not stopped. In DMA case, it
> causes DMA channel to be stuck because the transfer is still active causing
> following transfers to be queued but not computed.
>
> Cc: <stable@vger.kernel.org> #3.9+
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Thanks.
> Reported-by: Alexander Morozov <etesial@gmail.com>
> ---
> drivers/mmc/host/atmel-mci.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/mmc/host/atmel-mci.c b/drivers/mmc/host/atmel-mci.c
> index bdb84da..e9ea2fc 100644
> --- a/drivers/mmc/host/atmel-mci.c
> +++ b/drivers/mmc/host/atmel-mci.c
> @@ -582,6 +582,13 @@ static void atmci_timeout_timer(unsigned long data)
> if (host->mrq->cmd->data) {
> host->mrq->cmd->data->error = -ETIMEDOUT;
> host->data = NULL;
> + /*
> + * With some SDIO modules, sometimes DMA transfer hangs. If
> + * stop_transfer() is not called then the DMA request is not
> + * removed, following ones are queued and never computed.
> + */
> + if (host->state == STATE_DATA_XFER)
> + host->stop_transfer(host);
> } else {
> host->mrq->cmd->error = -ETIMEDOUT;
> host->cmd = NULL;
>
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: atmel-mci: abort transfer on timeout error
Date: Tue, 10 Sep 2013 09:54:39 +0200 [thread overview]
Message-ID: <522ED03F.5070404@atmel.com> (raw)
In-Reply-To: <1378740596-25026-1-git-send-email-ludovic.desroches@atmel.com>
On 09/09/2013 17:29, ludovic.desroches at atmel.com :
> From: Ludovic Desroches <ludovic.desroches@atmel.com>
>
> When a software timeout occurs, the transfer is not stopped. In DMA case, it
> causes DMA channel to be stuck because the transfer is still active causing
> following transfers to be queued but not computed.
>
> Cc: <stable@vger.kernel.org> #3.9+
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Thanks.
> Reported-by: Alexander Morozov <etesial@gmail.com>
> ---
> drivers/mmc/host/atmel-mci.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/mmc/host/atmel-mci.c b/drivers/mmc/host/atmel-mci.c
> index bdb84da..e9ea2fc 100644
> --- a/drivers/mmc/host/atmel-mci.c
> +++ b/drivers/mmc/host/atmel-mci.c
> @@ -582,6 +582,13 @@ static void atmci_timeout_timer(unsigned long data)
> if (host->mrq->cmd->data) {
> host->mrq->cmd->data->error = -ETIMEDOUT;
> host->data = NULL;
> + /*
> + * With some SDIO modules, sometimes DMA transfer hangs. If
> + * stop_transfer() is not called then the DMA request is not
> + * removed, following ones are queued and never computed.
> + */
> + if (host->state == STATE_DATA_XFER)
> + host->stop_transfer(host);
> } else {
> host->mrq->cmd->error = -ETIMEDOUT;
> host->cmd = NULL;
>
--
Nicolas Ferre
next prev parent reply other threads:[~2013-09-10 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 15:29 [PATCH] mmc: atmel-mci: abort transfer on timeout error ludovic.desroches
2013-09-09 15:29 ` ludovic.desroches at atmel.com
2013-09-10 7:54 ` Nicolas Ferre [this message]
2013-09-10 7:54 ` Nicolas Ferre
2013-09-26 1:46 ` Chris Ball
2013-09-26 1:46 ` Chris Ball
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=522ED03F.5070404@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=cjb@laptop.org \
--cc=etesial@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.