Lines Matching refs:bridge

18 Usually these ICs are connected to the main bridge driver through one or
231 bridge-specific per-subdev private data. The v4l2_subdev structure provides
235 From the bridge driver perspective you load the sub-device module and somehow
333 first (traditional) possibility is to have subdevices registered by bridge
334 drivers. This can be done when the bridge driver has the complete information
338 to SoCs, which pass information about them to bridge drivers, usually in their
342 asynchronously to bridge devices. An example of such a configuration is a Device
344 system independently from the bridge devices, e.g. when subdevices are defined
349 run-time bridge-subdevice interaction is in both cases the same.
351 In the synchronous case a device (bridge) driver needs to register the
395 be called. Before a bridge driver registers a subdev it can set sd->grp_id
397 bridge driver and the sub-device driver will never modify or use it.
399 The group ID gives the bridge driver more control how callbacks are called.
420 bridge driver availability. The subdevice driver then has to verify whether all
427 stored in a global list of subdevices, ready to be picked up by bridge drivers.
430 subdevice descriptors that the bridge device needs for its operation. This is
541 is called. This will unregister the sub-device from the bridge driver. It is
544 You need to do this because when the bridge driver destroys the i2c adapter
551 The bridge driver also has some helper functions it can use:
1138 respective bridge device. The Linux kernel provides a Common Clock Framework for
1144 a V4L2 clock helper API has been developed and is provided to bridge and