Lines Matching refs:sub

20 called 'sub-devices'.
27 connecting to sub-devices themselves. Some of this is quite complicated
49 2) A way of initializing and commanding sub-devices (if any).
62       +-sub-device instances
74 sub-device instances, the video_device struct stores V4L2 device node data
78 driver sets the struct v4l2_device mdev field, sub-devices and video nodes
118 You can also supply a notify() callback that can be called by sub-devices to
119 notify you of events. Whether you need to set this depends on the sub-device.
120 Any notifications a sub-device supports must be defined in a header in
209 Many drivers need to communicate with sub-devices. These devices can do all
211 encoding or decoding. For webcams common sub-devices are sensors and camera
215 driver with a consistent interface to these sub-devices the v4l2_subdev struct
218 Each sub-device driver must have a v4l2_subdev struct. This struct can be
219 stand-alone for simple sub-devices or it might be embedded in a larger struct
235 From the bridge driver perspective you load the sub-device module and somehow
238 Helper functions exists for sub-devices on an I2C bus that do most of this
241 Each v4l2_subdev contains function pointers that sub-device drivers can
242 implement (or leave NULL if it is not applicable). Since sub-devices can do
283 depending on the sub-device. E.g. a video device is unlikely to support the
289 A sub-device driver initializes the v4l2_subdev struct using:
312 Don't forget to cleanup the media entity before the sub-device is destroyed:
323 sub-devices. The driver is still responsible for validating the correctness
324 of the format configuration between sub-devices and video nodes.
360 If the v4l2_device parent device has a non-NULL mdev field, the sub-device
363 You can unregister a sub-device using:
381 It is also possible to call all or a subset of the sub-devices:
397 bridge driver and the sub-device driver will never modify or use it.
407 If the sub-device needs to notify its v4l2_device parent of an event, then
443 V4L2 sub-device userspace API
447 sub-devices can also be controlled directly by userspace applications.
449 Device nodes named v4l-subdevX can be created in /dev to access sub-devices
450 directly. If a sub-device supports direct userspace configuration it must set
453 After registering sub-devices, the v4l2_device driver can create device nodes
454 for all registered sub-devices marked with V4L2_SUBDEV_FL_HAS_DEVNODE by calling
456 removed when sub-devices are unregistered.
470 	controls implemented in the sub-device. Depending on the driver, those
480 	events generated by the sub-device. Depending on the driver, those
486 	sub-device. After registration events can be queued as usual on the
494 	All ioctls not in the above list are passed directly to the sub-device
498 I2C sub-device drivers
541 is called. This will unregister the sub-device from the bridge driver. It is
542 safe to call this even if the sub-device was never registered.
1085 			 struct v4l2_event_subscription *sub, unsigned elems,
1106 			   struct v4l2_event_subscription *sub)