ioctl VIDIOC_REQBUFS
&manvol;
VIDIOC_REQBUFSInitiate Memory Mapping or User Pointer I/Oint ioctlint fdint requeststruct v4l2_requestbuffers *argpArgumentsfd&fd;requestVIDIOC_REQBUFSargpDescriptionThis ioctl is used to initiate memory
mapped or user pointer
I/O. Memory mapped buffers are located in device memory and must be
allocated with this ioctl before they can be mapped into the
application's address space. User buffers are allocated by
applications themselves, and this ioctl is merely used to switch the
driver into user pointer I/O mode and to setup some internal structures.To allocate device buffers applications initialize all
fields of the v4l2_requestbuffers structure.
They set the type field to the respective
stream or buffer type, the count field to
the desired number of buffers, memory
must be set to the requested I/O method and the reserved array
must be zeroed. When the ioctl
is called with a pointer to this structure the driver will attempt to allocate
the requested number of buffers and it stores the actual number
allocated in the count field. It can be
smaller than the number requested, even zero, when the driver runs out
of free memory. A larger number is also possible when the driver requires
more buffers to function correctly. For example video output requires at least two buffers,
one displayed and one filled by the application.When the I/O method is not supported the ioctl
returns an &EINVAL;.Applications can call VIDIOC_REQBUFS
again to change the number of buffers, however this cannot succeed
when any buffers are still mapped. A count
value of zero frees all buffers, after aborting or finishing any DMA
in progress, an implicit &VIDIOC-STREAMOFF;.
struct v4l2_requestbuffers
&cs-str;
__u32countThe number of buffers requested or granted.&v4l2-buf-type;typeType of the stream or buffers, this is the same
as the &v4l2-format; type field. See for valid values.&v4l2-memory;memoryApplications set this field to
V4L2_MEMORY_MMAP or
V4L2_MEMORY_USERPTR.__u32reserved[2]A place holder for future extensions and custom
(driver defined) buffer types V4L2_BUF_TYPE_PRIVATE and
higher. This array should be zeroed by applications.
&return-value;
EBUSYThe driver supports multiple opens and I/O is already
in progress, or reallocation of buffers was attempted although one or
more are still mapped.EINVALThe buffer type (type field) or the
requested I/O method (memory) is not
supported.