Lines Matching refs:v4l2_device

6 Each device instance is represented by a struct v4l2_device.
13 	(dev, :c:type:`v4l2_dev <v4l2_device>`).
15 Registration will initialize the :c:type:`v4l2_device` struct. If the
17 :c:type:`v4l2_dev <v4l2_device>` argument.
21 that embed the struct v4l2_device instance. This is achieved by a
23 They must also set the struct v4l2_device mdev field to point to a
26 If :c:type:`v4l2_dev <v4l2_device>`\ ->name is empty then it will be set to a
30 :c:type:`v4l2_dev <v4l2_device>`\ ->name before calling
42 :c:type:`v4l2_dev <v4l2_device>` with a particular parent.
52 	(:c:type:`v4l2_dev <v4l2_device>`).
54 If the dev->driver_data field points to :c:type:`v4l2_dev <v4l2_device>`,
59 happens the parent device becomes invalid. Since :c:type:`v4l2_device` has a
64 	(:c:type:`v4l2_dev <v4l2_device>`).
81 		struct v4l2_device *v4l2_dev = dev_get_drvdata(dev);
120 safe to unregister :c:type:`v4l2_device` for hotpluggable devices. For this
121 purpose :c:type:`v4l2_device` has refcounting support. The refcount is
124 zero, then the :c:type:`v4l2_device` release() callback is called. You can
131 	(:c:type:`v4l2_dev <v4l2_device>`).
136 	(:c:type:`v4l2_dev <v4l2_device>`).
143 v4l2_device functions and data structures