struct vb2_queue — a videobuf queue
struct vb2_queue {
unsigned int type;
unsigned int io_modes;
struct device * dev;
const struct dma_attrs * dma_attrs;
unsigned fileio_read_once:1;
unsigned fileio_write_immediately:1;
unsigned allow_zero_bytesused:1;
unsigned quirk_poll_must_check_waiting_for_buffers:1;
struct mutex * lock;
void * owner;
const struct vb2_ops * ops;
const struct vb2_mem_ops * mem_ops;
const struct vb2_buf_ops * buf_ops;
void * drv_priv;
unsigned int buf_struct_size;
u32 timestamp_flags;
gfp_t gfp_flags;
u32 min_buffers_needed;
}; private buffer type whose content is defined by the vb2-core caller. For example, for V4L2, it should match the V4L2_BUF_TYPE_* in include/uapi/linux/videodev2.h
supported io methods (see vb2_io_modes enum)
device to use for the default allocation context if the driver
doesn't fill in the alloc_devs array.
DMA attributes to use for the DMA. May be NULL.
report EOF after reading the first buffer
queue buffer after each write call
allow bytesused == 0 to be passed to the driver
Return POLLERR at poll when QBUF has not been called. This is a vb1 idiom that has been adopted also by vb2.
pointer to a mutex that protects the vb2_queue struct. The driver can set this to a mutex to let the v4l2 core serialize the queuing ioctls. If the driver wants to handle locking itself, then this should be set to NULL. This lock is not used by the videobuf2 core API.
The filehandle that 'owns' the buffers, i.e. the filehandle that called reqbufs, create_buffers or started fileio. This field is not used by the videobuf2 core API, but it allows drivers to easily associate an owner filehandle with the queue.
driver-specific callbacks
memory allocator specific callbacks
callbacks to deliver buffer information between user-space and kernel-space
driver private data
size of the driver-specific buffer structure; “0” indicates the driver doesn't want to use a custom buffer structure type. for example, sizeof(struct vb2_v4l2_buffer) will be used for v4l2.
Timestamp flags; V4L2_BUF_FLAG_TIMESTAMP_* and V4L2_BUF_FLAG_TSTAMP_SRC_*
additional gfp flags used when allocating the buffers. Typically this is 0, but it may be e.g. GFP_DMA or __GFP_DMA32 to force the buffer allocation to a specific memory zone.
the minimum number of buffers needed before
start_streaming can be called. Used when a DMA engine
cannot be started unless at least this number of buffers
have been queued into the driver.