omap3-isp bt656 10bit

2016-07-28 Thread Eduard Gavin
Hello,

I'm trying to read 10 bit BT656 using an omap3 DM3730 (omap3-isp).

The bt565 data comes from ADV7842 configured manually from i2c, I have
checked the ADV configuration using an evaluation board
(EVAL-ADV7842-7511P) in BT656 10 bits mode. Then I assume that the
10bit BT656 arrives to the omap isp.

In the kernel side, I use a tvp5150 driver like a dummy driver in
order to configure the MC and V4L2, this dummy driver only have
patched the i2c read/write and is well registered.

My question is about 10bit instead of 8 bits of tvp5150, in the
omap3-isp driver the 10 bits for BT656 is not configured (the
ISPCCDC_CFG_BW656 is not set in ispccdc.c file)

I just added

isp_reg_set(isp, OMAP3_ISP_IOMEM_CCDC, ISPCCDC_CFG, ISPCCDC_CFG_BW656);

inside of ccdc_set_stream function, and I have checked that the bit 5
in 0x480B_C654 CCDC_CFG omap register and comes to "1"

But with yavta I can't capture the image sent from ADV7842, after
convert with raw2rgbpnm appear the "image", attached link.
http://picpaste.com/test-0HlXySLu.png

Any clue about how to use BT656 10 bits in omap3 (DM3730)?

I have tested with kernel v4.5 mainline and v4.3 that was used for
validate the tvp5150(bt656 8bit) video captures to omap3-isp.

Best Regards
Eduard Gavin
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


OMAP3 ISP BT656

2012-01-17 Thread Gary Thomas

I have a number of boards with OMAP 3530/3730 that use the
TVP5150AM1 video decoder.  On most of these boards, I can
capture reasonable quality video.  However, I have some (more
than a few which is reason for concern) where the video is
either really bad or even the ISP doesn't seem to recognize
the BT656 data stream.  On the ones that have bad video,
the data is all blown out and barely recognizable.

All the boards are running the same kernel (3.0+ with the
YUV patches that Lennart and others proposed late last year).
I've verified that the component registers (ISPCCDC and TVP5150)
match.  I can't see what could be the cause of such radically
variable behaviour.

The one thing I've found is on the boards that don't work
at all, the CCDC_SYN_MODE[FLDSTAT] bit is not toggling, which
in turn causes no data to be pushed through the V4L2 pipeline.

Any ideas what can cause this?  More importantly, what I can
try to fix it?  The really scary thing is that all the boards
in my lab work great, but in the factory (some 6000 miles away),
more than not don't work :-(

Would it be possible to configure the CCDC to capture the
raw BT656 data?  These boards are very small and it's impossible
to get onto the video data lines going into the processor (they
are all hidden within the circuit board).

Any help/ideas gladly accepted.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: OMAP3 ISP BT656

2012-01-17 Thread Gary Thomas

On 2012-01-17 14:50, Gary Thomas wrote:

I have a number of boards with OMAP 3530/3730 that use the
TVP5150AM1 video decoder. On most of these boards, I can
capture reasonable quality video. However, I have some (more
than a few which is reason for concern) where the video is
either really bad or even the ISP doesn't seem to recognize
the BT656 data stream. On the ones that have bad video,
the data is all blown out and barely recognizable.

All the boards are running the same kernel (3.0+ with the
YUV patches that Lennart and others proposed late last year).
I've verified that the component registers (ISPCCDC and TVP5150)
match. I can't see what could be the cause of such radically
variable behaviour.


Sorry, attribution should be to Laurent Pinchart :-)



The one thing I've found is on the boards that don't work
at all, the CCDC_SYN_MODE[FLDSTAT] bit is not toggling, which
in turn causes no data to be pushed through the V4L2 pipeline.

Any ideas what can cause this? More importantly, what I can
try to fix it? The really scary thing is that all the boards
in my lab work great, but in the factory (some 6000 miles away),
more than not don't work :-(

Would it be possible to configure the CCDC to capture the
raw BT656 data? These boards are very small and it's impossible
to get onto the video data lines going into the processor (they
are all hidden within the circuit board).

Any help/ideas gladly accepted.



--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html