dmaengine: edma: Correct the handling of src/dst_maxburst == 0
When clients asks for maxburst = 0 it is basically the same case as if they were asking for maxburst = 1 since in both case ASYNC need to be used and the eDMA is expected to write/read one word per DMA request. Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com> Acked-by: Joel Fernandes <joelf@ti.com> Reviewed-and-Tested-by: Joel Fernandes <joelf@ti.com> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
This commit is contained in:
parent
7cf2af90cd
commit
b2b617de04
|
@ -287,6 +287,10 @@ static int edma_config_pset(struct dma_chan *chan, struct edmacc_param *pset,
|
||||||
int absync;
|
int absync;
|
||||||
|
|
||||||
acnt = dev_width;
|
acnt = dev_width;
|
||||||
|
|
||||||
|
/* src/dst_maxburst == 0 is the same case as src/dst_maxburst == 1 */
|
||||||
|
if (!burst)
|
||||||
|
burst = 1;
|
||||||
/*
|
/*
|
||||||
* If the maxburst is equal to the fifo width, use
|
* If the maxburst is equal to the fifo width, use
|
||||||
* A-synced transfers. This allows for large contiguous
|
* A-synced transfers. This allows for large contiguous
|
||||||
|
|
Loading…
Reference in a new issue