On 14 August 2014 16:03, Matthieu CASTET <matthieu.castet@xxxxxxxxxx> wrote:
> When we wait for busy after sending a command, if there is
> a timeout, we got SDHCI_INT_DATA_TIMEOUT flags.
> Before this commit we got the message :
> "Got data interrupt 0x00100000 even though no data operation was in progress."
> and we need to wait 10s that sdhci_timeout_timer expires.
>
> Signed-off-by: Matthieu CASTET <matthieu.castet@xxxxxxxxxx>
Thanks! Applied for next.
Kind regards
Uffe
> ---
> drivers/mmc/host/sdhci.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
> index 47055f3..9df59a4 100644
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
> @@ -2301,6 +2301,11 @@ static void sdhci_data_irq(struct sdhci_host *host, u32 intmask)
> * above in sdhci_cmd_irq().
> */
> if (host->cmd && (host->cmd->flags & MMC_RSP_BUSY)) {
> + if (intmask & SDHCI_INT_DATA_TIMEOUT) {
> + host->cmd->error = -ETIMEDOUT;
> + tasklet_schedule(&host->finish_tasklet);
> + return;
> + }
> if (intmask & SDHCI_INT_DATA_END) {
> sdhci_finish_command(host);
> return;
> --
> 2.1.0.rc1
>
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
