diff options
| author | Seungwon Jeon <[email protected]> | 2012-05-20 13:27:21 +0900 |
|---|---|---|
| committer | Chris Ball <[email protected]> | 2012-06-06 09:35:47 -0400 |
| commit | eed6c63cefaf935e6fb28c4dd9977a280ae544a8 (patch) | |
| tree | c8be5ba50ffd562d35bccbb140bd4ba5644185e4 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 2a0fe914a38745f5b03534c4e4f4056cbd6978b8 (diff) | |
mmc: dw_mmc: fix the transmission handling in IDMAC
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 of DTO rising. This makes the
current request finish 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 <[email protected]>
Signed-off-by: Seungwon Jeon <[email protected]>
Signed-off-by: Hyeonsu Kim <[email protected]>
Acked-by: Will Newton <[email protected]>
Signed-off-by: Chris Ball <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions