Hi Philipp, On Fri, Oct 07, 2016 at 06:00:47PM +0200, Philipp Zabel wrote: > Currently the v4l2_async_notifier needs to be given a list of matches > for all expected subdevices on creation. When chaining subdevices that > are asynchronously probed via device tree, the bridge device that sets > up the notifier does not know the complete list of subdevices, as it > can only parse its own device tree node to obtain information about > the nearest neighbor subdevices. > To support indirectly connected subdevices, we need to support amending > the existing notifier waiting list with newly found neighbor subdevices > with each registered subdevice. Could you elaborate a little what's the exact use case for this? What kind of a device? Thanks. -- Kind regards, Sakari Ailus e-mail: sakari.ailus@xxxxxx XMPP: sailus@xxxxxxxxxxxxxx -- 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
