On Sun, May 20, 2012 at 5:27 AM, Seungwon Jeon <tgih.jun@xxxxxxxxxxx> 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@xxxxxxxxxxx> > Signed-off-by: Seungwon Jeon <tgih.jun@xxxxxxxxxxx> > --- > 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@xxxxxxxxxx> -- 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
