Re: [PATCHv4 1/8] videobuf2: rework vb2_mem_ops API
From: Sergey Senozhatsky <senozhatsky@chromium.org>
Date: 2021-08-17 10:41:16
Also in:
lkml
From: Sergey Senozhatsky <senozhatsky@chromium.org>
Date: 2021-08-17 10:41:16
Also in:
lkml
On (21/08/03 10:08), Hans Verkuil wrote:
On 27/07/2021 09:05, Sergey Senozhatsky wrote: Sprinkle a few more 'the's in the text:quoted
With new DMA API we need an extension of videobuf2 API. Previously,With -> With the of -> of thequoted
videobuf2 core would set non-coherent DMA bit in vb2 queue dma_attrvideobuf2 -> the videobuf2 set -> set the in vb2 queue dma_attr -> in the vb2_queue dma_attr fieldquoted
(if user-space would pass a corresponding memory hint); vb2 corevb2 core -> the vb2 corequoted
then would pass the vb2 queue dma_attrs to the vb2 allocators.vb2 queue -> vb2_queuequoted
vb2 allocator would use queue's dma_attr and DMA API would allocatevb2 -> The vb2 queue's -> the queue's DMA API -> the DMA APIquoted
either coherent or non-coherent memory. But we cannot do this anymore, since there is no corresponding DMA attr flag and, hence, there is no way for the allocator to become aware of what type of allocation user-space has requested. So we need to pass more context from videobuf2 core to the allocators. Fix this by changing call_ptr_memop() macro to pass vb2 pointer tochanging -> changing the vb2 pointer to -> the vb2 pointer to the
Ack... The Ack.