Hi Matsubara-san,
Katsuya MATSUBARA wrote:
Hi Vladimir,
From: Vladimir Barinov <vladimir.barinov@xxxxxxxxxxxxxxxxxx>
Date: Fri, 21 Jun 2013 14:32:05 +0400
Katsuya MATSUBARA wrote:
Hi Vladimir,
From: Vladimir Barinov <vladimir.barinov@xxxxxxxxxxxxxxxxxx>
Date: Fri, 21 Jun 2013 13:39:50 +0400
(snip)
I have not seen such i2c errors during capturing and booting.
But I have seen that querystd() in the ml86v7667 driver often
returns V4L2_STD_UNKNOWN, although the corresponding function
could you try Hans's fix:
https://patchwork.kernel.org/patch/2640701/
The fix has been already applied in my environment.
I've found that after some iteration of submission we disabled the
input signal in autodetection in ml86v7667_init(). per
recommendations.
That could be the case why the input signal is not locked.
On adv7180 it still has optional autodetection but Hans recommended to
get rid from runtime autodetection.
So I've added input signal detection only during boot time.
Could you please try the attached patch?
With the patch, V4L2_STD_UNKNOWN often returned by querystd()
in the ml86v7667 driver has been gone.
But, captured images are still incorrect that means wrong
order of fields desite '_BT' chosen for V4L2_STD_525_60.
I've ordered the NTSC camera.
I will return once I get it.
Regards,
Vladimir
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
