* [PATCH 1/4] mmc: dw_mmc: fix the transmission handling in IDMAC
@ 2012-05-20 4:27 Seungwon Jeon
2012-05-21 10:11 ` Will Newton
0 siblings, 1 reply; 2+ messages in thread
From: Seungwon Jeon @ 2012-05-20 4:27 UTC (permalink / raw)
To: linux-mmc
Cc: 'Chris Ball', 'Will Newton',
'James Hogan'
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
--
1.7.0.4
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH 1/4] mmc: dw_mmc: fix the transmission handling in IDMAC
2012-05-20 4:27 [PATCH 1/4] mmc: dw_mmc: fix the transmission handling in IDMAC Seungwon Jeon
@ 2012-05-21 10:11 ` Will Newton
0 siblings, 0 replies; 2+ messages in thread
From: Will Newton @ 2012-05-21 10:11 UTC (permalink / raw)
To: Seungwon Jeon; +Cc: linux-mmc, Chris Ball, James Hogan
On Sun, May 20, 2012 at 5:27 AM, Seungwon Jeon <tgih.jun@samsung.com> 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(-)
This looks ok, although I don't have any IDMAC hardware to test with.
Acked-by: Will Newton <will.newton@imgtec.com>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-05-21 10:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-20 4:27 [PATCH 1/4] mmc: dw_mmc: fix the transmission handling in IDMAC Seungwon Jeon
2012-05-21 10:11 ` Will Newton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox