提交 aba96bad 编写于 作者: V Vinod Koul

dmaengine: clarify the issue_pending expectations

Although Documentation explicitly mentions the expectations, the comment in
header can be lead to different expectation so clear up the confusion
Signed-off-by: NVinod Koul <vinod.koul@intel.com>
上级 939b6ef3
...@@ -447,7 +447,8 @@ struct dmaengine_unmap_data { ...@@ -447,7 +447,8 @@ struct dmaengine_unmap_data {
* communicate status * communicate status
* @phys: physical address of the descriptor * @phys: physical address of the descriptor
* @chan: target channel for this operation * @chan: target channel for this operation
* @tx_submit: set the prepared descriptor(s) to be executed by the engine * @tx_submit: accept the descriptor, assign ordered cookie and mark the
* descriptor pending. To be pushed on .issue_pending() call
* @callback: routine to call after this operation is complete * @callback: routine to call after this operation is complete
* @callback_param: general parameter to pass to the callback routine * @callback_param: general parameter to pass to the callback routine
* ---async_tx api specific fields--- * ---async_tx api specific fields---
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册