From: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
mchehab@redhat.com, linux-media@vger.kernel.org,
linux-sh@vger.kernel.org, matsu@igel.co.jp
Subject: Re: [PATCH v2 1/5] V4L2: I2C: ML86V7667 video decoder driver
Date: Mon, 22 Apr 2013 08:39:42 +0000 [thread overview]
Message-ID: <5174F74E.9030707@cogentembedded.com> (raw)
In-Reply-To: <201304220848.04870.hverkuil@xs4all.nl>
Hi Hans,
Thank you for the review.
Hans Verkuil wrote:
>> +#include <media/v4l2-chip-ident.h>
>>
>
> This include should be removed as well.
>
ok
>
>> +
>> +static int ml86v7667_querystd(struct v4l2_subdev *sd, v4l2_std_id *std)
>> +{
>> + struct ml86v7667_priv *priv = to_ml86v7667(sd);
>> +
>> + *std = priv->std;
>>
>
> That's not right. querystd should attempt to detect the standard, that's
> what it is for. It should just return the detected standard, not actually
> change it.
>
Ok.
I've mixed the things up with your review on removing the autoselection
feature and detection.
Thx for pointing on this.
>
>> + */
>> + val = i2c_smbus_read_byte_data(client, STATUS_REG);
>> + if (val < 0)
>> + return val;
>> +
>> + priv->std = val & STATUS_NTSCPAL ? V4L2_STD_PAL : V4L2_STD_NTSC;
>>
>
> Shouldn't this be 50 Hz vs 60 Hz formats? There are 60 Hz PAL standards
> and usually these devices detect 50 Hz vs 60 Hz, not NTSC vs PAL.
>
In the reference manual it is not mentioned about 50/60Hz input format
selection/detection but it mentioned just PAL/NTSC.
The 50hz formats can be ether PAL and NTSC formats variants. The same is
applied to 60Hz.
In the ML86V7667 datasheet the description for STATUS register detection
bit is just PAL/NTSC:
" $2C/STATUS [2] NTSC/PAL identification 0: NTSC /1: PAL "
If you assure me that I must judge their description as 50 vs 60Hz
formats and not PAL/NTSC then I will make the change.
Regards,
Vladimir
next prev parent reply other threads:[~2013-04-22 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 18:40 [PATCH v2 1/5] V4L2: I2C: ML86V7667 video decoder driver Sergei Shtylyov
2013-04-22 6:48 ` Hans Verkuil
2013-04-22 8:39 ` Vladimir Barinov [this message]
2013-04-22 9:06 ` Hans Verkuil
2013-04-22 20:55 ` Vladimir Barinov
2013-04-22 21:00 ` Vladimir Barinov
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=5174F74E.9030707@cogentembedded.com \
--to=vladimir.barinov@cogentembedded.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=matsu@igel.co.jp \
--cc=mchehab@redhat.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).