2011/9/20 Murali Krishna Palnati <palnati.muralikrishna@xxxxxxxxx>: > On Tue, Sep 20, 2011 at 4:05 PM, NamJae Jeon <linkinjeon@xxxxxxxxx> wrote: >> yes, I knew. But if card keep holding busy line(data 0) in the middle >> of DMA operation(multi blocks write), host driver layer can not know >> card status in this situation. > > The host driver shall start a software timer and indpendently needs to > watch out for the expiry of the timeout. If the host doesn't hear back > from the > controller/DMA engine even after waiting for the specified timeout, > then the timer handler that gets invoked can then do the necessary > cleanup and > inform the MMC core layer that the request failed. Does this sound feasible? > It may be no good choice that sw timer is on host driver. also I don't know what is different. It is the same as the ata driver's dma_map_sg. dma_map_sg is repectively called in mmc host driver. but it is being processed in ata core of ata driver. because it is common routine, ata core have called it instead of host driver. if it is processed in mmc core, there is no need to modify several hosts.(except dma controller reset) -- 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
