Hi, I am wondering if there already example of V4L2 capture drivers which can be used as either stand-alone bridge driver or as a sub-device to another bridge driver based on configuration. I am looking for some example I could use as a starting point. Given the following entities: - S :: CSI2 sensor - Cs :: CSI2 capture engine - Cp :: Parallel capture engine Here is the scenarios I have: Case #1: S => Cs Here Cs connect to S. Cs advertises video node. Driver Connectivity is established through DT using the v4l2-asynchronous registration method. Case #2: S => Cs => Cp Here Cs connect to S and Cp connects to Cs. Cp advertises a video node. In this case Cs appears as a "sensor" to Cp. Driver Connectivity is established through DT using the v4l2-asynchronous registration method. I would guess that the difficulty here would be within the Cs driver to setup the appropriate V4L2 device registration based on how DT is setup. If anyone as any example of this type, I would appreciate a few pointers/ideas or examples. Regards, Benoit -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
