Lines Matching full:will

67   file operation is called this lock will be taken by the core and released
84   If left to ``NULL``, then it will use the struct v4l2_prio_state
134 A reference to the entity will be automatically acquired/released when the
142 If you set this pointer, then that will be used by unlocked_ioctl to
147 set, then this lock will be used instead of :c:type:`video_device`->lock
162 function: if videobuf has to wait for a frame to arrive, then it will
168 In the case of :ref:`videobuf2 <vb2_framework>` you will need to implement the
184 This will create the character device for you.
195 the video device entity will be automatically registered with the media
215 device node number used (i.e. the X in ``videoX``). Normally you will pass -1
220 will attempt to select that device node number. If that number was already
221 in use, then the next free device node number will be selected and it
222 will send a warning to the kernel log.
228 and the v4l2 framework will try to pick the first free number that is equal
229 or higher to what you passed. If that fails, then it will just pick the
238 ``video0`` and you will see 'name', 'dev_debug' and 'index' attributes. The
262 it. The ``vdev->release()`` callback will never be called if the registration
304 This will remove the device nodes from sysfs (causing udev to remove them
310 release, of course) will return an error as well.