Hi Rafael, On Tue, Oct 03, 2017 at 02:04:50AM +0200, Rafael J. Wysocki wrote: > Hi, > > On Mon, Sep 11, 2017 at 9:59 AM, Sakari Ailus > <sakari.ailus@xxxxxxxxxxxxxxx> wrote: > > Hi folks, > > > > We have a large influx of new, unmerged, drivers that are now parsing > > fwnode endpoints and each one of them is doing this a little bit > > differently. The needs are still exactly the same for the graph data > > structure is device independent. This is still a non-trivial task and the > > majority of the driver implementations are buggy, just buggy in different > > ways. > > > > Facilitate parsing endpoints by adding a convenience function for parsing > > the endpoints, and make the omap3isp and rcar-vin drivers use them as an > > example. > > > > To show where we're getting with this, I've added support for async > > sub-device notifier support that is notifiers that can be registered by > > sub-device drivers as well as V4L2 fwnode improvements to make use of them > > and the DTS changes for the Nokia N9. Some of these patches I've posted > > previously in this set here: > > > > <URL:http://www.spinics.net/lists/linux-media/msg118764.html> > > > > Since that, the complete callback of the master notifier registering the > > V4L2 device is only called once all sub-notifiers have been completed as > > well. This way the device node creation can be postponed until all devices > > have been successfully initialised. > > > > With this, the as3645a driver successfully registers a sub-device to the > > media device created by the omap3isp driver. The kernel also has the > > information it's related to the sensor driven by the smiapp driver but we > > don't have a way to expose that information yet. > > I don't see core changes in this set, so I'm assuming it to be > targeted at the users of endpoints etc. Yes, this is dealing with V4L2 and how information from firmware is used mainly but there is also DT binding documentation. -- Kind regards, Sakari Ailus sakari.ailus@xxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
