Lines Matching full:subdevices

141 There are currently two ways to register subdevices with the V4L2 core. The
142 first (traditional) possibility is to have subdevices registered by bridge
144 about subdevices connected to it and knows exactly when to register them. This
145 is typically the case for internal subdevices, like video data processing units
150 There are however also situations where subdevices have to be registered
152 Tree based system where information about subdevices is made available to the
153 system independently from the bridge devices, e.g. when subdevices are defined
196 performed using the :c:func:`v4l2_async_unregister_subdev` call. Subdevices
197 registered this way are stored in a global list of subdevices, ready to be
278 registered subdevices to them. If a match is detected the ``.bound()`` notifier
356 and control subdevices through the :c:type:`v4l2_subdev_ops` operations in
414 Bridge drivers that control their connected subdevices through direct calls to
430 To create a read-only device node for all the subdevices registered with the