diff options
author | Sergey Senozhatsky <senozhatsky@chromium.org> | 2021-09-09 13:24:23 +0200 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab+huawei@kernel.org> | 2021-09-30 10:07:56 +0200 |
commit | a4b83deb3e76fb9385ca58e2c072a145b3a320d6 (patch) | |
tree | 7e06e86294a6c3a4082f2f7ff6302213e36baa10 /drivers/rtc/rtc-cmos.c | |
parent | 745b475e7e10ae1e8c538e5db89494411ee1c22b (diff) |
media: videobuf2: rework vb2_mem_ops API
With the new DMA API we need an extension of the videobuf2 API.
Previously, videobuf2 core would set the non-coherent DMA bit
in the vb2_queue dma_attr field (if user-space would pass a
corresponding memory hint); the vb2 core then would pass the
vb2_queue dma_attrs to the vb2 allocators. The vb2 allocator
would use the queue's dma_attr and the DMA API would allocate
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 the call_ptr_memop() macro to pass the
vb2 pointer to the corresponding op callbacks.
Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Diffstat (limited to 'drivers/rtc/rtc-cmos.c')
0 files changed, 0 insertions, 0 deletions