Lines Matching full:c

12 	:c:func:`v4l2_device_register <v4l2_device_register>`
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.
24 properly initialized and registered :c:type:`media_device` instance.
26 If :c:type:`v4l2_dev <v4l2_device>`\ ->name is empty then it will be set to a
28 If you set it up before  calling :c:func:`v4l2_device_register` then it will
30 :c:type:`v4l2_dev <v4l2_device>`\ ->name before calling
31 :c:func:`v4l2_device_register`.
33 You can use :c:func:`v4l2_device_set_name` to set the name based on a driver
42 :c:type:`v4l2_dev <v4l2_device>` with a particular parent.
51 	:c:func:`v4l2_device_unregister`
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
63 	:c:func:`v4l2_device_disconnect`
64 	(:c:type:`v4l2_dev <v4l2_device>`).
67 :c:func:`v4l2_device_unregister` function for that. If your driver is not
68 hotpluggable, then there is no need to call :c:func:`v4l2_device_disconnect`.
77 .. code-block:: c
109 .. code-block:: c
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
122 increased whenever :c:func:`video_register_device` is called and it is
124 zero, then the :c:type:`v4l2_device` release() callback is called. You can
130 	:c:func:`v4l2_device_get`
131 	(:c:type:`v4l2_dev <v4l2_device>`).
135 	:c:func:`v4l2_device_put`
136 	(:c:type:`v4l2_dev <v4l2_device>`).
139 :c:func:`v4l2_device_put` in the ``disconnect()`` callback (for USB devices)