Home
last modified time | relevance | path

Searched refs:buf_release (Results 1 – 4 of 4) sorted by relevance

/openbmc/linux/drivers/media/v4l2-core/
H A Dvideobuf-core.c170 BUG_ON(!q->ops->buf_release); in videobuf_queue_core_init()
254 q->ops->buf_release(q, q->bufs[i]); in __videobuf_free()
289 q->ops->buf_release(q, q->bufs[i]); in videobuf_queue_cancel()
592 q->ops->buf_release(q, buf); in videobuf_qbuf()
825 q->ops->buf_release(q, q->read_buf); in videobuf_read_zerocopy()
934 q->ops->buf_release(q, q->read_buf); in videobuf_read_one()
949 q->ops->buf_release(q, q->read_buf); in videobuf_read_one()
H A Dvideobuf-dma-sg.c417 q->ops->buf_release(q, q->bufs[i]); in videobuf_vm_close()
/openbmc/linux/include/media/
H A Dvideobuf-core.h110 void (*buf_release)(struct videobuf_queue *q, member
/openbmc/linux/Documentation/driver-api/media/
H A Dv4l2-videobuf.rst97 void (*buf_release)(struct videobuf_queue *q,
132 Finally, buf_release() is called when a buffer is no longer intended to be
157 should be used (it should be zero in the buf_release() case), and intr
267 so, they will all be passed to the buf_release() callback. If buffers