diff options
| author | Amelie Delaunay <[email protected]> | 2022-01-17 10:17:40 +0100 |
|---|---|---|
| committer | Vinod Koul <[email protected]> | 2022-02-15 11:12:07 +0530 |
| commit | 728f6c783313fc789197837dce1f97d1f930cafe (patch) | |
| tree | b31e0de6179a0b34550a5b2a3233f804b06ed4a7 /tools/testing/selftests/bpf/progs/test_prog_array_init.c | |
| parent | 177360e04b70b1d3937471e42201cdbb831a82da (diff) | |
dmaengine: stm32-dma: set dma_device max_sg_burst
Some stm32-dma consumers [1] rather use dma_get_slave_caps() to get
max_sg_burst of their DMA channel as dma_get_max_seg_size() is specific to
the DMA controller.
All stm32-dma channels have the same features so, don't need to implement
device_caps ops. Let dma_get_slave_caps() relies on dma_device
configuration.
That's why this patch sets dma_device max_sg_burst to the maximum segment
size, which is the maximum of data items that can be transferred without
software intervention.
[1] https://lore.kernel.org/lkml/[email protected]/
"media: stm32: dcmi: create a dma scatterlist based on DMA max_sg_burst value"
Signed-off-by: Amelie Delaunay <[email protected]>
Tested-by: Alain Volmat <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Vinod Koul <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/progs/test_prog_array_init.c')
0 files changed, 0 insertions, 0 deletions