Lines Matching refs:v4l2_device

4 Each device instance is represented by a struct :c:type:`v4l2_device`.
11 	(dev, :c:type:`v4l2_dev <v4l2_device>`).
13 Registration will initialize the :c:type:`v4l2_device` struct. If the
15 :c:type:`v4l2_dev <v4l2_device>` argument.
19 that embed the struct :c:type:`v4l2_device` instance. This is achieved by a
21 They must also set the struct :c:type:`v4l2_device` mdev field to point to a
24 If :c:type:`v4l2_dev <v4l2_device>`\ ->name is empty then it will be set to a
28 :c:type:`v4l2_dev <v4l2_device>`\ ->name before calling
40 :c:type:`v4l2_dev <v4l2_device>` with a particular parent.
50 	(:c:type:`v4l2_dev <v4l2_device>`).
52 If the dev->driver_data field points to :c:type:`v4l2_dev <v4l2_device>`,
57 happens the parent device becomes invalid. Since :c:type:`v4l2_device` has a
62 	(:c:type:`v4l2_dev <v4l2_device>`).
79 		struct v4l2_device *v4l2_dev = dev_get_drvdata(dev);
118 safe to unregister :c:type:`v4l2_device` for hotpluggable devices. For this
119 purpose :c:type:`v4l2_device` has refcounting support. The refcount is
122 zero, then the :c:type:`v4l2_device` release() callback is called. You can
129 	(:c:type:`v4l2_dev <v4l2_device>`).
134 	(:c:type:`v4l2_dev <v4l2_device>`).
141 v4l2_device functions and data structures