From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: "Jon Arne Jørgensen" <jonarne@jonarne.no>
Cc: mchehab@redhat.com, linux-media@vger.kernel.org,
jonjon.arnearne@gmail.com
Subject: Re: [PATCH V2 3/3] saa7115: Add register setup and config for gm7113c
Date: Thu, 2 May 2013 23:24:07 -0300 [thread overview]
Message-ID: <20130503022406.GD5722@localhost> (raw)
In-Reply-To: <1367268069-11429-4-git-send-email-jonarne@jonarne.no>
On Mon, Apr 29, 2013 at 10:41:09PM +0200, Jon Arne Jørgensen wrote:
>
> Signed-off-by: Jon Arne Jørgensen <jonarne@jonarne.no>
Every patch *must* have a proper commit message indicating what you're doing
and why you're doing it.
In particular, please add as much information as you can about this new clone decoder.
If you know *why* we have to add those quirks for PAL and NTSC, it would
be nice to add that information to the commit message and maybe even
in a comment somewhere in the code.
> ---
> drivers/media/i2c/saa7115.c | 48 ++++++++++++++++++++++++++++++++++++---------
> 1 file changed, 39 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/media/i2c/saa7115.c b/drivers/media/i2c/saa7115.c
> index eb2c19d..77c13dc 100644
> --- a/drivers/media/i2c/saa7115.c
> +++ b/drivers/media/i2c/saa7115.c
> @@ -126,6 +126,8 @@ static int saa711x_has_reg(const int id, const u8 reg)
> return 0;
>
> switch (id) {
> + case V4L2_IDENT_GM7113C:
> + return reg != 0x14 && (reg < 0x18 || reg > 0x1e) && reg < 0x20;
> case V4L2_IDENT_SAA7113:
> return reg != 0x14 && (reg < 0x18 || reg > 0x1e) && (reg < 0x20 || reg > 0x3f) &&
> reg != 0x5d && reg < 0x63;
> @@ -447,6 +449,30 @@ static const unsigned char saa7115_cfg_50hz_video[] = {
>
> /* ============== SAA7715 VIDEO templates (end) ======= */
>
> +/* ============== GM7113C VIDEO templates ============= */
> +static const unsigned char gm7113c_cfg_60hz_video[] = {
> + R_08_SYNC_CNTL, 0x68, /* 0xBO: auto detection, 0x68 = NTSC */
> + R_0E_CHROMA_CNTL_1, 0x07, /* video autodetection is on */
> +
> +#if 0
> + R_5A_V_OFF_FOR_SLICER, 0x06, /* standard 60hz value for ITU656 line counting */
> +#endif
What's the meaning of this ifdef? In general it's better to remove dead
code, or at least to put some fat comment about it.
> + 0x00, 0x00
> +};
> +
> +static const unsigned char gm7113c_cfg_50hz_video[] = {
> + R_08_SYNC_CNTL, 0x28, /* 0x28 = PAL */
> + R_0E_CHROMA_CNTL_1, 0x07,
> +
> +#if 0
> + R_5A_V_OFF_FOR_SLICER, 0x03, /* standard 50hz value */
> +#endif
Ditto.
I've tested this with an stk1160/gm7113c device and now
it's working fine (NTSC, PAL-M, PAL-Nc).
I also tested against regressions using stk1160/saa7113 and
em28xx/saa7115 devices.
I must admit I'm quite happy to have this issue finally fixed!
Could you please re-send the whole series, taking account of this
comments. You can add my:
Tested-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
to every patch in the series.
Thanks!
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-05-03 2:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 20:41 [PATCH 0/3] saa7115: add detection code for gm7113c Jon Arne Jørgensen
2013-04-29 20:41 ` [PATCH V2 1/3] saa7115: move the autodetection code out of the probe function Jon Arne Jørgensen
2013-05-03 2:09 ` Ezequiel Garcia
2013-05-03 6:32 ` Jon Arne Jørgensen
2013-05-03 11:37 ` Mauro Carvalho Chehab
2013-05-03 6:58 ` Jon Arne Jørgensen
2013-05-03 11:20 ` Ezequiel Garcia
2013-05-03 12:08 ` Mauro Carvalho Chehab
2013-05-05 8:20 ` Jon Arne Jørgensen
2013-05-05 11:29 ` Mauro Carvalho Chehab
2013-04-29 20:41 ` [PATCH V2 2/3] saa7115: add detection code for gm7113c Jon Arne Jørgensen
2013-05-03 2:10 ` Ezequiel Garcia
2013-04-29 20:41 ` [PATCH V2 3/3] saa7115: Add register setup and config " Jon Arne Jørgensen
2013-05-03 2:24 ` Ezequiel Garcia [this message]
2013-05-03 6:35 ` Jon Arne Jørgensen
2013-05-03 2:00 ` [PATCH 0/3] saa7115: add detection code " Ezequiel Garcia
2013-05-03 6:27 ` Jon Arne Jørgensen
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=20130503022406.GD5722@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=jonarne@jonarne.no \
--cc=jonjon.arnearne@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.