Commit 4303a0c9 authored Feb 06, 2017 by Sakari Ailus Committed by Mauro Carvalho Chehab Jul 19, 2017

media: dt: bindings: Explicitly specify bus type



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, or the bus type
cannot be automatically detected.

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.

Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
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>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>

parent 8056402c

Documentation/devicetree/bindings/media/video-interfaces.txt

+5 −0

Original line number	Diff line number	Diff line
		@@ -76,6 +76,11 @@ 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
		- 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