V4L2源代码之旅十一:videobuf主要结构体

1. vb2_mem_ops

/**
 * struct vb2_mem_ops - memory handling/memory allocator operations
 * @alloc:    allocate video memory and, optionally, allocator private data,()
 *        return NULL on failure or a pointer to allocator private,
 *        per-buffer data on success; the returned private structure
 *        will then be passed as buf_priv argument to other ops in this
 *        structure
 * @put:    inform(通知) the allocator that the buffer will no longer be used;
 *        usually will result in the allocator freeing the buffer (if
 *        no other users of this buffer are present); the buf_priv
 *        argument is the allocator private per-buffer structure
 *        previously returned from the alloc callback
 * @get_userptr: acquire userspace memory for a hardware operation; used for
 *         USERPTR memory types; vaddr is the address passed to the
 *         videobuf layer when queuing a video buffer of USERPTR type;
 *         should return an allocator private per-buffer structure
 *         associated with the buffer on success, NULL on failure;
 *         the returned private structure will then be passed as buf_priv
 *         argument to other ops in this structure    为一个硬件操作来获取userspace memory,用于内存类型是:USERPTR;当 queing 一个USERPTR类型的video buffer,vadd 是一个被传递到videobuf layer的地址。
 * @put_userptr: inform the allocator that a USERPTR buffer will no longer
 *         be used(通知allocator,USERPTR buffer不再使用)
 * @vaddr:    return a kernel virtual address to a given memory buffer
 *        associated with the passed private structure or NULL if no
 *        such mapping exists(返回内核虚拟地址)
 * @cookie:    return allocator specific cookie for a given memory buffer
 *        associated with the passed private structure or NULL if not
 *        available(返回allocator特定的cookie)
 * @num_users:    return the current number of users of a memory buffer;
 *        return 1 if the videobuf layer (or actually the driver using
 *        it) is the only user
 * @mmap:    setup a userspace mapping for a given memory buffer under
 *        the provided virtual memory region
 *
 * Required ops for USERPTR types: get_userptr, put_userptr.
 * Required ops for MMAP types: alloc, put, num_users, mmap.
 * Required ops for read/write access types: alloc, put, num_users, vaddr
 */
struct vb2_mem_ops {
    void        *(*alloc)(void *alloc_ctx, unsigned long size);
    void        (*put)(void *buf_priv);

    void        *(*get_userptr)(void *alloc_ctx, unsigned long vaddr,
                    unsigned long size, int write);
    void        (*put_userptr)(void *buf_priv);

    void        *(*vaddr)(void *buf_priv);
    void        *(*cookie)(void *buf_priv);

    unsigned int    (*num_users)(void *buf_priv);

    int        (*mmap)(void *buf_priv, struct vm_area_struct *vma);
};

2. vb2_io_modes

/**
 * enum vb2_io_modes - queue access methods
 * @VB2_MMAP:        driver supports MMAP with streaming API
 * @VB2_USERPTR:    driver supports USERPTR with streaming API
 * @VB2_READ:        driver supports read() style access
 * @VB2_WRITE:        driver supports write() style access
 */
enum vb2_io_modes {
    VB2_MMAP    = (1 << 0),
    VB2_USERPTR    = (1 << 1),
    VB2_READ    = (1 << 2),
    VB2_WRITE    = (1 << 3),
};

  对于Camera这种流数据,通常是使用VB2_MMAP或VB2_USERPTR。

3. vb2_buffer_state

/**
 * enum vb2_buffer_state - current video buffer state
 * @VB2_BUF_STATE_DEQUEUED:    buffer under userspace control
 * @VB2_BUF_STATE_QUEUED:    buffer queued in videobuf, but not in driver
 * @VB2_BUF_STATE_ACTIVE:    buffer queued in driver and possibly used
 *                in a hardware operation
 * @VB2_BUF_STATE_DONE:        buffer returned from driver to videobuf, but
 *                not yet dequeued to userspace
 * @VB2_BUF_STATE_ERROR:    same as above, but the operation on the buffer
 *                has ended with an error, which will be reported
 *                to the userspace when it is dequeued
 */
enum vb2_buffer_state {
    VB2_BUF_STATE_DEQUEUED,   // buffer处于userspace的控制
    VB2_BUF_STATE_QUEUED,     // buffer被queued到videobuf中,但是不在driver中
    VB2_BUF_STATE_ACTIVE,     // buffer被queued到driver中,而且有可能硬件正在访问该buffer.
    VB2_BUF_STATE_DONE,       // buffer由driver返回到videobuf中,但是还未dequeued到userspace
    VB2_BUF_STATE_ERROR,      // buffer在操作过程中发生错误,而且该错误在dequeued时,报告到userspace
};

4. vb2_buffer

/**
 * struct vb2_buffer - represents a video buffer
 * @v4l2_buf:        struct v4l2_buffer associated with this buffer; can
 *            be read by the driver and relevant entries can be
 *            changed by the driver in case of CAPTURE types
 *            (such as timestamp)
 * @v4l2_planes:    struct v4l2_planes associated with this buffer; can
 *            be read by the driver and relevant entries can be
 *            changed by the driver in case of CAPTURE types
 *            (such as bytesused); NOTE that even for single-planar
 *            types, the v4l2_planes[0] struct should be used
 *            instead of v4l2_buf for filling bytesused - drivers
 *            should use the vb2_set_plane_payload() function for that
 * @vb2_queue:        the queue to which this driver belongs
 * @num_planes:        number of planes in the buffer
 *            on an internal driver queue
 * @state:        current buffer state; do not change
 * @queued_entry:    entry on the queued buffers list, which holds all
 *            buffers queued from userspace
 * @done_entry:        entry on the list that stores all buffers ready to
 *            be dequeued to userspace
 * @planes:        private per-plane information; do not change
 * @num_planes_mapped:    number of mapped planes; do not change
 */
struct vb2_buffer {
    struct v4l2_buffer    v4l2_buf;                     // CAPTURE:可以由driver读写
    struct v4l2_plane    v4l2_planes[VIDEO_MAX_PLANES];             // CAPTURE:可以由driver读写,(byteused)即使是对于single-planar类型,v4l2_planes[0]应该被使用而不是仅仅使用v4l2_buf的byteused。            // 驱动使用改函数vb2_set_plane_payload()设置byteused.

    struct vb2_queue    *vb2_queue;  // 该vb2_buffer所属的vb2_queue

    unsigned int        num_planes;  // 该buffer有多少个planes

/* Private: internal use only */
    enum vb2_buffer_state    state;  // buffer的当前状态

    struct list_head    queued_entry; // queued buffer 链表,保存所有从userspace queued进的buffers
    struct list_head    done_entry;   // 保存所有准备 dequeued 到userspace的buffers链表

    struct vb2_plane    planes[VIDEO_MAX_PLANES];  // 私有的 per-plane 信息,驱动禁止修改
    unsigned int        num_planes_mapped;         // mapped plane
};

5. vb2_ops

/**
 * struct vb2_ops - driver-specific callbacks
 *
 * @queue_setup:    called from a VIDIOC_REQBUFS handler, before
 *            memory allocation; driver should return the required
 *            number of buffers in num_buffers, the required number
 *            of planes per buffer in num_planes; the size of each
 *            plane should be set in the sizes[] array and optional
 *            per-plane allocator specific context in alloc_ctxs[]
 *            array    在分配内存之前,发送VIDIOC_REQBUFS命令时调用。driver应该在该回调函数中设置num_buffers,the number of planes per buffer;每个plane的size,    有时会设置特定于不同环境的per-plane allocator。
 * @wait_prepare:    release any locks taken while calling vb2 functions;
 *            it is called before an ioctl needs to wait for a new
 *            buffer to arrive; required to avoid a deadlock in
 *            blocking access type    当调用vb2函数时,释放所持有的锁; 在一个需要等待一个新的buffer到来的ioctl之前调用;在阻塞访问下需要防止死锁
 * @wait_finish:    reacquire all locks released in the previous callback;
 *            required to continue operation after sleeping while
 *            waiting for a new buffer to arrive    获取所有之前释放的锁
 * @buf_init:        called once after allocating a buffer (in MMAP case)
 *            or after acquiring a new USERPTR buffer; drivers may
 *            perform additional buffer-related initialization;
 *            initialization failure (return != 0) will prevent
 *            queue setup from completing successfully; optional    对于MMAP类型,分配buffer后立刻调用;对于USERPTR在获取一个buffer后调用;驱动可能执行一些附加的buffer相关的初始化;
 * @buf_prepare:    called every time the buffer is queued from userspace;
 *            drivers may perform any initialization required before
 *            each hardware operation in this callback;
 *            if an error is returned, the buffer will not be queued
 *            in driver; optional    每次buffer从userspace queued都会被调用,在硬件操作buffer之前,驱动可能会执行一些初始化;如果返回失败,buffer不会被queued到驱动中
 * @buf_finish:        called before every dequeue of the buffer back to
 *            userspace; drivers may perform any operations required
 *            before userspace accesses the buffer; optional    每次dequeue buffer在返回 userspace 之前调用;驱动可能在 userspace 访问buffer之前做一些操作
 * @buf_cleanup:    called once before the buffer is freed; drivers may
 *            perform any additional cleanup; optional    当buffer释放时调用,驱动可能执行一些附加的清理工作
 * @start_streaming:    called once before entering ‘streaming‘ state; enables
 *            driver to receive buffers over buf_queue() callback
 * @stop_streaming:    called when ‘streaming‘ state must be disabled; driver
 *            should stop any DMA transactions or wait until they
 *            finish and give back all buffers it got from buf_queue()
 *            callback; may use vb2_wait_for_all_buffers() function    当‘streaming’状态被清除时调用;驱动应该停止任何DMA传输或者等待直到DMA操作结束并且返回通过buf_queue()拿到的所有的buffer。可能使用vb2_wait_for_all_buffers()
 * @buf_queue:        passes buffer vb to the driver; driver may start
 *            hardware operation on this buffer; driver should give
 *            the buffer back by calling vb2_buffer_done() function    将buffer传递到driver;driver可能开始对该buffer进行硬件操作;driver应该通过调用vb2_buffer_done()函数将归还buffer
 */
struct vb2_ops {
    int (*queue_setup)(struct vb2_queue *q, unsigned int *num_buffers,
               unsigned int *num_planes, unsigned long sizes[],
               void *alloc_ctxs[]);

    void (*wait_prepare)(struct vb2_queue *q);
    void (*wait_finish)(struct vb2_queue *q);

    int (*buf_init)(struct vb2_buffer *vb);
    int (*buf_prepare)(struct vb2_buffer *vb);
    int (*buf_finish)(struct vb2_buffer *vb);
    void (*buf_cleanup)(struct vb2_buffer *vb);

    int (*start_streaming)(struct vb2_queue *q);
    int (*stop_streaming)(struct vb2_queue *q);

    void (*buf_queue)(struct vb2_buffer *vb);
};

6. vb2_queue

/**
 * struct vb2_queue - a videobuf queue
 *
 * @type:    queue type (see V4L2_BUF_TYPE_* in linux/videodev2.h
 * @io_modes:    supported io methods (see vb2_io_modes enum)
 * @io_flags:    additional io flags (see vb2_fileio_flags enum)
 * @ops:    driver-specific callbacks
 * @mem_ops:    memory allocator specific callbacks
 * @drv_priv:    driver private data
 * @buf_struct_size: size of the driver-specific buffer structure;
 *        "0" indicates the driver doesn‘t want to use a custom buffer
 *        structure type, so sizeof(struct vb2_buffer) will is used
 *
 * @memory:    current memory type used
 * @bufs:    videobuf buffer structures
 * @num_buffers: number of allocated/used buffers
 * @queued_list: list of buffers currently queued from userspace
 * @queued_count: number of buffers owned by the driver
 * @done_list:    list of buffers ready to be dequeued to userspace
 * @done_lock:    lock to protect done_list list
 * @done_wq:    waitqueue for processes waiting for buffers ready to be dequeued
 * @alloc_ctx:    memory type/allocator-specific contexts for each plane
 * @streaming:    current streaming state
 * @fileio:    file io emulator internal data, used only if emulator is active
 */
struct vb2_queue {
    enum v4l2_buf_type        type;
    unsigned int            io_modes;
    unsigned int            io_flags;

    const struct vb2_ops        *ops;
    const struct vb2_mem_ops    *mem_ops;
    void                *drv_priv;
    unsigned int            buf_struct_size;

/* private: internal use only */
    enum v4l2_memory        memory;
    struct vb2_buffer        *bufs[VIDEO_MAX_FRAME];
    unsigned int            num_buffers;

    struct list_head        queued_list;

    atomic_t            queued_count;
    struct list_head        done_list;
    spinlock_t            done_lock;
    wait_queue_head_t        done_wq;

    void                *alloc_ctx[VIDEO_MAX_PLANES];

    unsigned int            streaming:1;

    struct vb2_fileio_data        *fileio;
};
时间: 2024-08-25 07:41:21

V4L2源代码之旅十一:videobuf主要结构体的相关文章

V4L2源代码之旅十:videobuf

关于videobuf,即V4L2如何实现高性能的和用户空间的Buffer交互,这部分内容应该是V4L2中最难以理解的部分了. 看文档:kernel/Documentation/video4linux/videobuf. videobuf的功能是V4L2 driver和user space之间的粘合层.为存储video frames分配和管理buffer.这是一组许多基于标准POSIX I/O系统调用都可以使用和实现的函数集,包括read(), poll(), and mmap().另外一组函数集

V4L2源代码之旅一:struct v4l2_device

一. 文档位置:linux-3.08/Documentation/video4linux/v4l2-framework.txt 二.翻译总结: V4L2驱动程序往往是很复杂的,其原因是硬件的复杂性:大多数设备有多个IC,从而导出多个设备节点/dev,并且创建了non-V4L2设备如DVB.ALSA,FB,I2C和输入(IR)设备. 特别的是,V4L2驱动必须组织IC支持完成音/视频的混流/编码/解码,这就导致V4L2驱动更加复杂.通常,这些IC是由一个或多个I2C总线连接到主桥驱动,其他总线也可

V4L2源代码之旅三:V4L2 sub-device userspace API

除了通过v4l2_subdev_ops结构体暴露kernel API,V4L2 sub-devices也可以被用户空间应用直接控制. v4l-subdevX的设备节点可以在/dev下被创建来直接访问sub-devices.如果一个sub-device支持用户空间直接配置,必须在注册前设置V4L2_SUBDEV_FL_HAS_DEVNODE标志.注册sub-devices之后,v4l2_device驱动会为所有标记了V4L2_SUBDEV_FL_HAS_DEVNODE标志的sub-devices创

V4L2源代码之旅七:源码追踪

1. v4l2_device_register /* kernel/drivers/media/video/v4l2-device.c */ int v4l2_device_register(struct device *dev, struct v4l2_device *v4l2_dev) { if (v4l2_dev == NULL) return -EINVAL; INIT_LIST_HEAD(&v4l2_dev->subdevs); // 初始化一个将要挂在v4l2_device上的子

V4L2源代码之旅三:I2C sub-device drivers

v4l2-common.h 对一个I2C驱动添加v4l2_subdev支持的建议方式是将v4l2_subdev嵌入到每一个I2C设备实例的state struct.如果设备非常简单,可以直接创建v4l2_subdev. 典型的state struct类似如下: struct chipname_state { struct v4l2_subdev sd; ... /* additional state fields */ }; v4l2_subdev结构体的初始化: v4l2_i2c_subdev

23、V4L2应用编写及各个ioctl涉及结构体说明

常用的结构体在内核目录include/linux/videodev2.h中定义 struct v4l2_requestbuffers  //申请帧缓冲,对应命令VIDIOC_REQBUFSstruct v4l2_capability      //视频设备的功能,对应命令VIDIOC_QUERYCAPstruct v4l2_input           //视频输入信息,对应命令VIDIOC_ENUMINPUTstruct v4l2_standard        //视频的制式,比如PAL,

linux内核中的hlist_head、list_head、hlist_node结构体

在linux内核中经常会看到这几个结构体: struct list_head; struct hlist_head; struct hlist_node; 在linux内核源代码中对这三个结构体的定义如下: struct list_head { struct list_head *prev; struct list_head *next; } struct hlist_node { struct hlist_node **prev; struct hlist_node *next; } stru

C语言结构体初始化的四种方法

定义 struct InitMember{    int first:    double second:    char* third:    float four;}; 方法一:定义时赋值 struct InitMember test = {-10,3.141590,"method one",0.25}: 需要注意对应的顺序,不能错位.方法二:定义后逐个赋值 struct InitMember test: test.first = -10;test.second = 3.14159

FFmpeg源代码分析:结构体成员管理系统-AVOption

本文继续上篇文章<FFmpeg源代码分析:结构体成员管理系统-AVClass>中的内容,记录FFmpeg中和AVOption相关的源代码.AVOption用于在FFmpeg中描述结构体中的成员变量.一个AVOption可以包含名称,简短的帮助信息,取值等等. 上篇文章简单回顾 上篇文章中概括了AVClass,AVOption和目标结构体之间的关系.以AVFormatContext为例,可以表示为下图. 有关上篇文章的内容,这里不再重复.总体来说,上篇文章主要概括了AVClass,AVOptio