From: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
To: Katsuya MATSUBARA <matsu@igel.co.jp>
Cc: sergei.shtylyov@cogentembedded.com, g.liakhovetski@gmx.de,
mchehab@redhat.com, linux-media@vger.kernel.org,
magnus.damm@gmail.com, linux-sh@vger.kernel.org,
phil.edworthy@renesas.com
Subject: Re: [PATCH v6] V4L2: soc_camera: Renesas R-Car VIN driver
Date: Sat, 22 Jun 2013 11:45:10 +0000 [thread overview]
Message-ID: <51C58E46.6000801@cogentembedded.com> (raw)
In-Reply-To: <20130621.220444.280357674.matsu@igel.co.jp>
Hi Matsubara-san,
Katsuya MATSUBARA wrote:
> Hi Vladimir,
>
> From: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
> Date: Fri, 21 Jun 2013 14:32:05 +0400
>
>
>> Katsuya MATSUBARA wrote:
>>
>>> Hi Vladimir,
>>>
>>> From: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
>>> 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
next prev parent reply other threads:[~2013-06-22 11:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 22:11 [PATCH v6] V4L2: soc_camera: Renesas R-Car VIN driver Sergei Shtylyov
2013-06-02 18:56 ` Sergei Shtylyov
2013-06-04 1:08 ` Simon Horman
2013-06-13 13:12 ` Guennadi Liakhovetski
2013-06-21 0:50 ` Vladimir Barinov
2013-06-21 20:08 ` Sergei Shtylyov
2013-06-21 4:46 ` Katsuya MATSUBARA
2013-06-21 8:06 ` Vladimir Barinov
2013-06-21 9:09 ` Katsuya MATSUBARA
2013-06-21 9:39 ` Vladimir Barinov
2013-06-21 10:01 ` Katsuya MATSUBARA
2013-06-21 10:32 ` Vladimir Barinov
2013-06-21 13:04 ` Katsuya MATSUBARA
2013-06-22 11:45 ` Vladimir Barinov [this message]
2013-07-25 3:01 ` [PATCH v8] " Katsuya MATSUBARA
2013-07-25 6:55 ` Vladimir Barinov
2013-07-25 7:29 ` Katsuya MATSUBARA
2013-07-26 11:11 ` Guennadi Liakhovetski
2013-07-30 7:36 ` Katsuya MATSUBARA
2013-07-30 7:45 ` Guennadi Liakhovetski
-- strict thread matches above, loose matches on Subject: below --
2013-07-19 23:14 Sergei Shtylyov
2013-07-24 16:14 ` Guennadi Liakhovetski
2013-07-24 19:36 ` Vladimir Barinov
2013-07-24 20:38 ` Guennadi Liakhovetski
2013-07-24 19:40 ` Sergei Shtylyov
2013-07-24 20:26 ` Guennadi Liakhovetski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51C58E46.6000801@cogentembedded.com \
--to=vladimir.barinov@cogentembedded.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=matsu@igel.co.jp \
--cc=mchehab@redhat.com \
--cc=phil.edworthy@renesas.com \
--cc=sergei.shtylyov@cogentembedded.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).