Hi Vinod,
On 25/08/2020 14.02, Vinod Koul wrote:
>> The only thing which might be an issue is that with the DMA_PREP_CMD the
>> config_data is dma_addr_t (via dmaengine_prep_slave_single).
>
> Yes I came to same conclusion
>
>>> I did have a prototype with metadata but didnt work very well, the
Hi Peter,
On 25-08-20, 11:00, Peter Ujfalusi wrote:
> Hi Vinod,
>
> On 25/08/2020 10.10, Vinod Koul wrote:
> >>> /**
> >>> * struct dma_slave_config - dma slave channel runtime config
> >>> * @direction: whether the data shall go in or out on this slave
> >>> @@ -418,6 +485,10 @@ enum dma_sl
Hi Vinod,
On 25/08/2020 10.10, Vinod Koul wrote:
>>> /**
>>> * struct dma_slave_config - dma slave channel runtime config
>>> * @direction: whether the data shall go in or out on this slave
>>> @@ -418,6 +485,10 @@ enum dma_slave_buswidth {
>>> * @slave_id: Slave requester id. Only valid fo
Hello Peter,
On 25-08-20, 09:52, Peter Ujfalusi wrote:
> Hi Vinod,
>
> On 24/08/2020 11.47, Vinod Koul wrote:
> > Some complex dmaengine controllers have capability to program the
> > peripheral device, so pass on the peripheral configuration as part of
> > dma_slave_config
> >
> > Signed-off-by
Hi Vinod,
On 24/08/2020 11.47, Vinod Koul wrote:
> Some complex dmaengine controllers have capability to program the
> peripheral device, so pass on the peripheral configuration as part of
> dma_slave_config
>
> Signed-off-by: Vinod Koul
> ---
> include/linux/dmaengine.h | 75 ++
5 matches
Mail list logo
