Lines Matching +full:transfer +full:- +full:function

11 pre-fetch makes the cache overhead relatively significant. If the DMA
13 transfer, the DMA preparation overhead would not affect the MMC performance.
15 The intention of non-blocking (asynchronous) MMC requests is to minimize the
19 dma_unmap_sg are processing. Using non-blocking MMC requests makes it
26 The mmc_blk_issue_rw_rq() in the MMC block driver is made non-blocking.
35 in parallel with the transfer performance won't be affected.
40 https://wiki.linaro.org/WorkingGroups/Kernel/Specs/StoragePerfMMC-async-req
45 There is one new public function mmc_start_req().
47 It starts a new MMC command request for a host. The function isn't
48 truly non-blocking. If there is an ongoing async request it waits
56 There are two optional members in the mmc_host_ops -- pre_req() and
57 post_req() -- that the host driver may implement in order to move work
58 to before and after the actual mmc_host_ops.request() function is called.
67 with the previous transfer, since there is no previous request.
73 and finally prepare the second chunk and start the transfer.
77   if (is_first_req && req->size > threshold)
78      /* start MMC transfer for the complete transfer size */
86       * the transfer is delayed, guesstimate max 4k as first chunk size.
90       dma_issue_pending(req->dma_desc);
96        * before this call, the transfer is delayed.
98       dma_issue_pending(req->dma_desc);