On 2018-04-05 04:33 PM, Ioan Nicu wrote:
Once the dma request is passed to the DMA engine, the DMA
subsystem would hold a pointer to this structure and could
call the completion callback after do_dma_request() has
timed out.
The current code deals with this by putting timed out SYNC
requests
On 2018-04-05 04:33 PM, Ioan Nicu wrote:
Once the dma request is passed to the DMA engine, the DMA
subsystem would hold a pointer to this structure and could
call the completion callback after do_dma_request() has
timed out.
The current code deals with this by putting timed out SYNC
requests
Once the dma request is passed to the DMA engine, the DMA
subsystem would hold a pointer to this structure and could
call the completion callback after do_dma_request() has
timed out.
The current code deals with this by putting timed out SYNC
requests to a pending list and freeing them later,
Once the dma request is passed to the DMA engine, the DMA
subsystem would hold a pointer to this structure and could
call the completion callback after do_dma_request() has
timed out.
The current code deals with this by putting timed out SYNC
requests to a pending list and freeing them later,
Once the dma request is passed to the DMA engine, the DMA
subsystem would hold a pointer to this structure and could
call the completion callback after do_dma_request() has
timed out.
The current code deals with this by putting timed out SYNC
requests to a pending list and freeing them later,
Once the dma request is passed to the DMA engine, the DMA
subsystem would hold a pointer to this structure and could
call the completion callback after do_dma_request() has
timed out.
The current code deals with this by putting timed out SYNC
requests to a pending list and freeing them later,
6 matches
Mail list logo