| Message ID | 20170206094956.GA17974@amd (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
Hi Pavel, On Mon, Feb 06, 2017 at 10:49:57AM +0100, Pavel Machek wrote: > From: Sakari Ailus <sakari.ailus@iki.fi> > > In the vast majority of cases the bus type is known to the driver(s) > since a receiver or transmitter can only support a single one. There > are cases however where different options are possible. > > The existing V4L2 OF support tries to figure out the bus type and > parse the bus parameters based on that. This does not scale too well > as there are multiple serial busses that share common properties. > > Some hardware also supports multiple types of busses on the same > interfaces. > > Document the CSI1/CCP2 property strobe. It signifies the clock or > strobe mode. Thanks. I split this into two (bus type + strobe). The result is in here: <URL:https://git.linuxtv.org/sailus/media_tree.git/commit/?h=ccp2> How about the rest? :-) I guess we could get the CCP2 support in omap3isp without the video bus switch. It'd be nice to have this in a single patchset.
On Mon, Feb 06, 2017 at 10:49:57AM +0100, Pavel Machek wrote: > From: Sakari Ailus <sakari.ailus@iki.fi> > > In the vast majority of cases the bus type is known to the driver(s) > since a receiver or transmitter can only support a single one. There > are cases however where different options are possible. > > The existing V4L2 OF support tries to figure out the bus type and > parse the bus parameters based on that. This does not scale too well > as there are multiple serial busses that share common properties. > > Some hardware also supports multiple types of busses on the same > interfaces. > > Document the CSI1/CCP2 property strobe. It signifies the clock or > strobe mode. > > Signed-off-by: Sakari Ailus <sakari.ailus@iki.fi> > Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com> > Signed-off-by: Pavel Machek <pavel@ucw.cz> > Reviewed-By: Sebastian Reichel <sre@kernel.org> Acked-by: Rob Herring <robh@kernel.org> -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/media/video-interfaces.txt b/Documentation/devicetree/bindings/media/video-interfaces.txt index 9cd2a36..6986fde 100644 --- a/Documentation/devicetree/bindings/media/video-interfaces.txt +++ b/Documentation/devicetree/bindings/media/video-interfaces.txt @@ -76,6 +76,12 @@ Optional endpoint properties mode horizontal and vertical synchronization signals are provided to the slave device (data source) by the master device (data sink). In the master mode the data source device is also the source of the synchronization signals. +- bus-type: data bus type. Possible values are: + 0 - autodetect based on other properties (MIPI CSI-2 D-PHY, parallel or Bt656) + 1 - MIPI CSI-2 C-PHY + 2 - MIPI CSI1 + 3 - CCP2 + Autodetection is default, and bus-type property may be omitted in that case. - bus-width: number of data lines actively used, valid for the parallel busses. - data-shift: on the parallel data busses, if bus-width is used to specify the number of data lines, data-shift can be used to specify which data lines are @@ -112,7 +118,8 @@ Optional endpoint properties should be the combined length of data-lanes and clock-lanes properties. If the lane-polarities property is omitted, the value must be interpreted as 0 (normal). This property is valid for serial busses only. - +- strobe: Whether the clock signal is used as clock or strobe. Used + with CCP2, for instance. Example -------