Home
last modified time | relevance | path

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

/linux-5.19.10/drivers/media/v4l2-core/
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()
Dvideobuf-dma-sg.c421 q->ops->buf_release(q, q->bufs[i]); in videobuf_vm_close()
/linux-5.19.10/include/media/
Dvideobuf-core.h110 void (*buf_release)(struct videobuf_queue *q, member
/linux-5.19.10/Documentation/driver-api/media/
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
/linux-5.19.10/drivers/media/pci/bt8xx/
Dbttv-vbi.c228 .buf_release = vbi_buffer_release,
Dbttv-driver.c1679 .buf_release = buffer_release,
/linux-5.19.10/drivers/media/common/saa7146/
Dsaa7146_vbi.c316 .buf_release = buffer_release,
Dsaa7146_video.c1169 .buf_release = buffer_release,
/linux-5.19.10/drivers/staging/media/atomisp/pci/
Datomisp_fops.c643 .buf_release = atomisp_buf_release,
650 .buf_release = atomisp_buf_release_output,
/linux-5.19.10/drivers/media/pci/cx18/
Dcx18-streams.c238 .buf_release = buffer_release,
/linux-5.19.10/drivers/media/usb/zr364xx/
Dzr364xx.c427 .buf_release = buffer_release,
/linux-5.19.10/drivers/media/usb/tm6000/
Dtm6000-video.c791 .buf_release = buffer_release,
/linux-5.19.10/drivers/media/platform/nxp/
Dfsl-viu.c546 .buf_release = buffer_release,
/linux-5.19.10/drivers/media/platform/ti/davinci/
Dvpfe_capture.c1251 .buf_release = vpfe_videobuf_release,