snip
[MK]In that case can't the driver just ignore the field polarity? I
assume that drivers implement the parameter that has support in hardware.
So it is not an issue.
No, because the same driver runs on hardware that also has the field
signal. So we need to be able to give information about
+
+struct v4l2_subdev_bus {
+ enum v4l2_subdev_bus_type type;
+ u8 width;
+ /* 0 - active low, 1 - active high */
+ unsigned pol_vsync:1;
+ /* 0 - active low, 1 - active high */
+ unsigned pol_hsync:1;
+ /* 0 - low to high , 1 - high to low */
+
+/*
+ * Some sub-devices are connected to the bridge device through a bus
that + * carries * the clock, vsync, hsync and data. Some interfaces
such as BT.656 + * carries the sync embedded in the data where as
others have separate line + * carrying the sync signals. The structure
From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com
re-sending with RFC in the header
This patch adds support for setting bus parameters such as bus type
(BT.656, BT.1120 etc), width (example 10 bit raw image data bus)
and polarities (vsync, hsync, field etc) in sub device. This
On Tuesday 09 June 2009 22:55:53 m-kariche...@ti.com wrote:
From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com
re-sending with RFC in the header
This patch adds support for setting bus parameters such as bus type
(BT.656, BT.1120 etc), width (example 10 bit raw image data bus)
On Tuesday 09 June 2009 23:03:01 Hans Verkuil wrote:
On Tuesday 09 June 2009 22:55:53 m-kariche...@ti.com wrote:
From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com
re-sending with RFC in the header
This patch adds support for setting bus parameters such as bus type
] adding support for setting bus parameters in sub
device
On Tuesday 09 June 2009 22:55:53 m-kariche...@ti.com wrote:
From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com
re-sending with RFC in the header
This patch adds support for setting bus parameters such as bus type
(BT.656
