public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: Seungwon Jeon <tgih.jun@samsung.com>
Cc: linux-mmc@vger.kernel.org, 'Chris Ball' <cjb@laptop.org>,
	'Will Newton' <will.newton@imgtec.com>,
	'James Hogan' <james.hogan@imgtec.com>,
	hyeonsu.kim@samsung.com
Subject: Re: [PATCH v2 1/4] mmc: dw_mmc: fix the transmission handling in IDMAC
Date: Wed, 23 May 2012 13:18:26 +0900	[thread overview]
Message-ID: <4FBC6512.8070400@samsung.com> (raw)
In-Reply-To: <006801cd37cf$7ca2e2a0$75e8a7e0$%jun@samsung.com>

Hi Seungwon,

This patch is already sent from Hyeonsu Kim,
Plz check the below patch.
Add Hyeonsu to CC'd

http://comments.gmane.org/gmane.linux.kernel.mmc/12870

Best Regards,
Jaehoon Chung

On 05/22/2012 01:00 PM, Seungwon Jeon wrote:

> DTO interrupt can be later than transmit interrupt(IDMAC)
> in case of write. Current handling of idmac interrupt sets
> EVENT_DATA_COMPLETE as well as EVENT_XFER_COMPLETE regardless
> DTO rising. This makes the current request be finished in tasklet
> and permits the next request even though current data transfer
> is still in progress. As a result, sequence is broken and lock-up
> happens. Setting EVENT_DATA_COMPLETE is not proper after IDMAC
> interrupt. It should be taken after DTO interrupt is generated.
> 
> Reported-by: Dmitry Shmidt <dimitrysh@android.com>
> Signed-off-by: Seungwon Jeon <tgih.jun@samsung.com>
> ---
>  drivers/mmc/host/dw_mmc.c |    1 -
>  1 files changed, 0 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
> index 9bbf45f..b46faf0 100644
> --- a/drivers/mmc/host/dw_mmc.c
> +++ b/drivers/mmc/host/dw_mmc.c
> @@ -1623,7 +1623,6 @@ static irqreturn_t dw_mci_interrupt(int irq, void *dev_id)
>  	if (pending & (SDMMC_IDMAC_INT_TI | SDMMC_IDMAC_INT_RI)) {
>  		mci_writel(host, IDSTS, SDMMC_IDMAC_INT_TI | SDMMC_IDMAC_INT_RI);
>  		mci_writel(host, IDSTS, SDMMC_IDMAC_INT_NI);
> -		set_bit(EVENT_DATA_COMPLETE, &host->pending_events);
>  		host->dma_ops->complete(host);
>  	}
>  #endif



  reply	other threads:[~2012-05-23  4:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22  4:00 [PATCH v2 1/4] mmc: dw_mmc: fix the transmission handling in IDMAC Seungwon Jeon
2012-05-23  4:18 ` Jaehoon Chung [this message]
2012-05-23  6:26   ` Seungwon Jeon
2012-05-23  7:18     ` Jaehoon Chung

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=4FBC6512.8070400@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=cjb@laptop.org \
    --cc=hyeonsu.kim@samsung.com \
    --cc=james.hogan@imgtec.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=tgih.jun@samsung.com \
    --cc=will.newton@imgtec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox