Re: [PATCH v3 2/3] v4l: fwnode: Support generic parsing of graph endpoints in a device

Hi Laurent, On Wed, Aug 23, 2017 at 03:59:35PM +0300, Laurent Pinchart wrote: > Hi Sakari, > > On Wednesday, 23 August 2017 12:01:24 EEST Sakari Ailus wrote: > > On Tue, Aug 22, 2017 at 03:52:33PM +0300, Laurent Pinchart wrote: > > > On Friday, 18 August 2017 14:23:16 EEST Sakari Ailus wrote: >

Re: [PATCH v3 2/3] v4l: fwnode: Support generic parsing of graph endpoints in a device

Hi Sakari, On Wednesday, 23 August 2017 12:01:24 EEST Sakari Ailus wrote: > On Tue, Aug 22, 2017 at 03:52:33PM +0300, Laurent Pinchart wrote: > > On Friday, 18 August 2017 14:23:16 EEST Sakari Ailus wrote: > >> The current practice is that drivers iterate over their endpoints and > >> parse each

Re: [PATCH v3 2/3] v4l: fwnode: Support generic parsing of graph endpoints in a device

Hi Laurent, Thanks for the critique. On Tue, Aug 22, 2017 at 03:52:33PM +0300, Laurent Pinchart wrote: > Hi Sakari, > > Thank you for the patch. > > On Friday, 18 August 2017 14:23:16 EEST Sakari Ailus wrote: > > The current practice is that drivers iterate over their endpoints and > > parse

Re: [PATCH v3 2/3] v4l: fwnode: Support generic parsing of graph endpoints in a device

Hi Sakari, Thank you for the patch. On Friday, 18 August 2017 14:23:16 EEST Sakari Ailus wrote: > The current practice is that drivers iterate over their endpoints and > parse each endpoint separately. This is very similar in a number of > drivers, implement a generic function for the job.

[PATCH v3 2/3] v4l: fwnode: Support generic parsing of graph endpoints in a device

The current practice is that drivers iterate over their endpoints and parse each endpoint separately. This is very similar in a number of drivers, implement a generic function for the job. Driver specific matters can be taken into account in the driver specific callback. Convert the omap3isp as