Re: [RFC 03/13] v4l: split lane parsing code

2017-02-14 Thread Pavel Machek
Hi! > On Tue, Feb 14, 2017 at 02:39:41PM +0100, Pavel Machek wrote: > > From: Sakari Ailus > > > > The function to parse CSI2 bus parameters was called > > v4l2_of_parse_csi_bus(), rename it as v4l2_of_parse_csi2_bus() in > > anticipation of CSI1/CCP2 support. > > > > Obtain data bus type from

Re: [RFC 03/13] v4l: split lane parsing code

2017-02-14 Thread Pavel Machek
Hi! > And you can remove CSI2 and PARALLEL cases. Ok, that's all easy enough. Thanks, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) h

Re: [RFC 03/13] v4l: split lane parsing code

2017-02-14 Thread Sakari Ailus
Hi Pavel, On Tue, Feb 14, 2017 at 02:39:41PM +0100, Pavel Machek wrote: > From: Sakari Ailus > > The function to parse CSI2 bus parameters was called > v4l2_of_parse_csi_bus(), rename it as v4l2_of_parse_csi2_bus() in > anticipation of CSI1/CCP2 support. > > Obtain data bus type from bus-type p

Re: [RFC 03/13] v4l: split lane parsing code

2017-02-14 Thread Sakari Ailus
Hi Pavel, On Tue, Feb 14, 2017 at 02:39:41PM +0100, Pavel Machek wrote: > From: Sakari Ailus > > The function to parse CSI2 bus parameters was called > v4l2_of_parse_csi_bus(), rename it as v4l2_of_parse_csi2_bus() in > anticipation of CSI1/CCP2 support. > > Obtain data bus type from bus-type p

[RFC 03/13] v4l: split lane parsing code

2017-02-14 Thread Pavel Machek
From: Sakari Ailus The function to parse CSI2 bus parameters was called v4l2_of_parse_csi_bus(), rename it as v4l2_of_parse_csi2_bus() in anticipation of CSI1/CCP2 support. Obtain data bus type from bus-type property. Only try parsing bus specific properties in this case. Separate lane parsing