driver-api/dmaengine/provider.rst

71 destination addresses, whether it should increment these addresses or
114 - ``channels``: should be initialized as a list using the
118   should contain a bitmask of the supported source transfer width
121   should contain a bitmask of the supported destination transfer width
124   should contain a bitmask of the supported slave directions
142 - ``dev``: should hold the pointer to the ``struct device`` associated
246   - The driver should return DMA_OUT_OF_ORDER for device_tx_status if
249   - All cookie tracking and checking API should be treated as invalid if
265   - This feature is limited to interleaved transfers, this flag should thus not
268     should be added in the future if and when the need arises.
309     The data from the provided metadata buffer should be prepared for the DMA
331     Should return a pointer for the metadata buffer, the maximum size of the
373     for the transfer being prepared, and should create a hardware
378   - Any allocation you might do should be using the GFP_NOWAIT
382   - Drivers should try to pre-allocate any memory they might need
386   - It should return a unique instance of the
397       should it be always the flags passed in the arguments
421     should move to the next transaction in the list.
427   - Should report the bytes left to go over on the given channel
429   - Should only care about the transaction descriptor passed as
434   - Should use dma_set_residue to report it
436   - In the case of a cyclic transfer, it should only take into
439   - Should return DMA_OUT_OF_ORDER if the device does not support in order
448   - This command should NOT perform synchronously, or on any
459   - This call is mandatory for slave operations only. This should NOT be
461     If a driver support both, it should use this call for slave
468   - This command should operate synchronously on the channel,
475   - This command should operate synchronously on the channel,
482   - For aborted transfers the complete callback should not be called
510 (stuff that should be documented, but don't really know
515 - Should be called at the end of an async TX transfer, and can be
540 - If set, the descriptor can be reused after being completed. It should
543 - The descriptor should be prepared for reuse by invoking
571     writes for which the descriptor should be in different format from
615 You should avoid this kind of practice, and instead of electing a new