Lines Matching refs:then

103 If v4l2_dev->name is empty then it will be set to a value derived from dev
105 calling v4l2_device_register then it will be untouched. If dev is NULL, then
110 etc. If the name ends with a digit, then it will insert a dash: cx18-0,
130 If you have a hotpluggable device (e.g. a USB device), then when a disconnect
139 then there is no need to call v4l2_device_disconnect().
186 If you have multiple device nodes then it can be difficult to know when it is
190 is released. When the refcount reaches zero, then the v4l2_device release()
193 If other device nodes (e.g. ALSA) are created, then you can increase and
391 errors (except -ENOIOCTLCMD) occurred, then 0 is returned.
393 The second argument to both calls is a group ID. If 0, then all subdevs are
394 called. If non-zero, then only those whose group ID match that value will
407 If the sub-device needs to notify its v4l2_device parent of an event, then
420 bridge driver availability. The subdevice driver then has to verify whether all
436 V4L2 core will then use these descriptors to match asynchronously registered
558 If all goes well, then it registers the subdev with the v4l2_device.
579 0 then that will be used (non-probing variant), otherwise the probed_addrs
590 If the subdev supports the s_config core ops, then that op is called with
611 If you embed it in a larger struct, then you must set the release()
642   future!), then set this to your v4l2_ioctl_ops struct. The vfl_type and
654   If queue is non-NULL, and queue->lock is non-NULL, then queue->lock is
663   If left to NULL, then it will use the struct v4l2_prio_state in v4l2_device.
665   then you can point it to your own struct v4l2_prio_state.
678 If you use v4l2_ioctl_ops, then you should set .unlocked_ioctl to video_ioctl2
716 this pointer, then that will be used by unlocked_ioctl to serialize all ioctls.
718 If you are using the videobuf2 framework, then there is a second lock that you
719 can set: video_device->queue->lock. If set, then this lock will be used instead
732 If you use the old videobuf then you must pass the video_device lock to the
734 arrive, then it will temporarily unlock the lock and relock it afterwards. If
735 your driver also waits in the code, then you should do the same to allow other
741 pointer, then you can use the helper functions vb2_ops_wait_prepare/finish.
745 video_device->queue->lock, then you have to first lock video_device->queue->lock
777 option. That number is then passed to this function and video_register_device
779 in use, then the next free device node number will be selected and it
787 or higher to what you passed. If that fails, then it will just pick the
808 After the device was successfully registered, then you can use these fields:
815 If the registration failed, then you need to call video_device_release()
845 of the driver or because the USB device was disconnected, then you should
858 When the last user of the video device node exits, then the vdev->release()
1009 If struct v4l2_fh is not embedded, then you can use these helper functions:
1046 object such as a control ID. If unused, then the ID is 0.
1051 lots of events of one type in a short time, then that will not overwrite
1055 reserved, then the oldest event will be dropped and the new one added.
1093   then the framework will fill in a default value (this depends on the event