Lines Matching refs:ioctls

468 	The controls ioctls are identical to the ones defined in V4L2. They
478 	The events ioctls are identical to the ones defined in V4L2. They
492 Private ioctls
494 	All ioctls not in the above list are passed directly to the sub-device
655   used for the queuing ioctls (VIDIOC_REQBUFS, CREATE_BUFS, QBUF, DQBUF,
657   That way the vb2 queuing framework does not have to wait for other ioctls.
684 your v4l2_ioctl_ops should be ignored. You can mark such ioctls by calling this
711 ioctls and locking
716 this pointer, then that will be used by unlocked_ioctl to serialize all ioctls.
720 of video_device->lock to serialize all queuing ioctls (see the previous section
721 for the full list of those ioctls).
723 The advantage of using a different lock for the queuing ioctls is that for some
726 ioctls. That way your VIDIOC_DQBUF doesn't stall because the driver is busy
830 0x01: Log the ioctl name and error code. VIDIOC_(D)QBUF ioctls are only logged
832 0x02: Log the ioctl name arguments and error code. VIDIOC_(D)QBUF ioctls are
838       VIDIOC_DQBUF ioctls.