On 07/29/2013 01:44 PM, Vinod Koul wrote:
> Please look into the residue field
>
> /**
> * struct dma_tx_state - filled in to report the status of
> * a transfer.
> * @last: last completed DMA cookie
> * @used: last issued DMA cookie (i.e. the one in progress)
> * @residue: the remaining number of bytes left to transmit
> * on the selected transfer for states DMA_IN_PROGRESS and
> * DMA_PAUSED if this is implemented in the driver, else 0
> */
> struct dma_tx_state {
> dma_cookie_t last;
> dma_cookie_t used;
> u32 residue;
> };
>
> Typically this is set to 0 when DMA_SUCCESS is returned for the
> dmaengine_tx_status() API. But in your case I feel its perfectly valid to return
> DMA_SUCCESS but with a non zero residue indiactaing how much was not transmitted
Thank you very much for that feedback. This has been already pointed
out to me and I converted my driver to use this. Once I finish adding
a few pieces I re-post the driver.
>
> ~Vinod
>
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
