Namjae Jeon wrote:
host controller can not rise timeout interrupt in write not read in DMA status.
because host can just know whether card is finish to program to use busy line.
If unstable card is keep holding busy line while writing using DMA.
hang problem happen by wait_for_completion. so I think that mmc driver need some exception to avoid this problem.
I suggest to use wait_for_completion_timeout instead of wait_for_completion.
I see what you are trying to solve, but you can never calculate the
timeout for this type of operation in such a way. Your timeout involves
the entire data write operation, how can you ever know how long this
will take?
I think a much better approach is to make you host driver not using
"busy signaling" (if that is possible), thus when the DMA job is done
call mmc_request_done to finalize the data transfer. The mmc framework
will then send a CMD13 (SEND_STATUS) to make sure the data is written
before issuing the next request.
BR
Ulf Hansson
--
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
