On Wed, Jul 30, 2014 at 11:01 PM, Laurent Pinchart
<laurent.pinch...@ideasonboard.com> wrote:
> Hi Enrico,
>
> On Wednesday 23 July 2014 15:57:51 Enrico wrote:
>> On Wed, Jul 23, 2014 at 3:54 PM, Enrico wrote:
>
> [snip]
>
>> > You were right i was using the wrong binary, now the output is:
>> >
>> > ...
>> > - entity 5: OMAP3 ISP CCDC (3 pads, 9 links)
>> > type V4L2 subdev subtype Unknown flags 0
>> > device node name /dev/v4l-subdev2
>> > pad0: Sink
>> > [fmt:UYVY2X8/720x625 field:interlaced]
>> > ...
>> > pad1: Source
>> > [fmt:UYVY/720x624 field:interlaced
>> > crop.bounds:(0,0)/720x624
>> > crop:(0,0)/720x624]
>> > ...
>> > - entity 16: tvp5150 1-005c (1 pad, 1 link)
>> > type V4L2 subdev subtype Unknown flags 0
>> > device node name /dev/v4l-subdev8
>> > pad0: Source
>> > [fmt:UYVY2X8/720x625 field:interlaced]
>
> That's surprising. Have you applied the tvp5150 patches from the
> omap3isp/bt656 branch ? The field should be hardcoded to V4L2_FIELD_ALTERNATE
> (reported as "alternate" by media-ctl), as the tvp5150 alternates between the
> top and bottom fields in consecutive frames. The CCDC input should then be
> configured to V4L2_FIELD_ALTERNATE as well, and the CCDC output to
> V4L2_FIELD_ALTERNATE ("alternate"), V4L2_FIELD_INTERLACED_TB ("interlaced-tb")
> or V4L2_FIELD_INTERLACED_BT ("interlaced-bt").
No, i missed those patches i was using only the omap3isp patches you
posted here.
With those patches and configuring the pipleline as you suggested i
could finally capture some good frames with yavta.
But i think there is some race, because it's not very "reliable". This
is what i see:
(with yavta -c50 -f UYVY -s 720x576 --field interlaced-tb /dev/video2)
1) first run, ok
2) if i re-run it soon after it finishes, it just hangs on start (in
VIDIOC_DQBUF).
I have to stop it with ctrl+c and after some seconds it exits, and the
kernel prints the ccdc stop timeout message.
in any case when it doesn't hang i can capture 200 frames with no
errors. And if i wait some seconds before running it again it usually
works (not always).
3) if i add -F to yavta (saving to a tmpfs in ram), it hangs after
capturing some frames (usually between 20 and 30).
yet again, same ctrl+c thing (it exits, ccdc stop timeout...).
Apart from these issues your patches are much better then the old
ones! Any hints on what i can try to fix these issues?
Thanks,
Enrico
--
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
