All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Francois Moine <moinejf@free.fr>
To: Luiz Ramos <lramos.prof@yahoo.com.br>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] Fix wrong register mask in gspca/sonixj.c
Date: Thu, 21 Jul 2011 13:27:01 +0200	[thread overview]
Message-ID: <20110721132701.2a305d8e@tele> (raw)
In-Reply-To: <1311244993.60601.YahooMailClassic@web121810.mail.ne1.yahoo.com>

On Thu, 21 Jul 2011 03:43:13 -0700 (PDT)
Luiz Ramos <lramos.prof@yahoo.com.br> wrote:

> Now my doubts. Unless I misunderstood something, it seems these are
> the our assumptions regarding reg01 and reg17:
> 
>   - reg01 bit 6 is set when bridge runs at 48 MHz; if reset, 24 MHz
>   - reg17 bits 0..4 is a mask for dividing a sensor clock of 48 MHz,
> so
>     - if reg17 = x | 01 then clock = 48 MHz
>     - if reg17 = x | 02 then clock = 24 MHz
>     - if reg17 = x | 04 then clock = 12 MHz
> 
> Putting some printk at the code version 2.13.3, the values of these
> registers at the last command are:
> 
>   - at 640x480 ........... reg01 = 0x66  reg17 = 0x64
>   - at 320x240/160x120 ... reg01 = 0x26  reg17 = 0x61
> 
> So, at 640x480 the bridge would be running at 48 MHz and the sensor
> at 12 MHz. At lower resolutions the bridge would be running at 24 MHz
> and the sensor at 48 MHz. It seems that this is not what we'd like to
> do.

>From the documentation, the register 17 contains a divide factor of the
bridge clock (the sensor has no clock). So:

- reg01 = 0x66  reg17 = 0x64 --> bridge 48 MHz sensor 12 MHz
- reg01 = 0x26  reg17 = 0x61 --> bridge 24 MHz sensor 24 MHz

> I made some experiences, and noticed that:
> 
>   - making reg17 = 0x62 (sensor clock at 24 MHz) and reg01 = 0x26
>     (bridge clock at 24 MHz) at 320x240 and lower makes it work again.
>     I think this reaches the goal of having both clocks at 24 MHz, but
>     at 10 fps

In fact, bridge 24 MHz and sensor 12 MHz. This seems the best
configuration.

-- 
Ken ar c'hentañ	|	      ** Breizh ha Linux atav! **
Jef		|		http://moinejf.free.fr/

      reply	other threads:[~2011-07-21 11:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15  2:08 [PATCH] Fix wrong register mask in gspca/sonixj.c Luiz Ramos
2011-07-15  7:48 ` Jean-Francois Moine
2011-07-15  9:57   ` Luiz Ramos
2011-07-15 17:44     ` Jean-Francois Moine
2011-07-19  1:39       ` Luiz Ramos
2011-07-20 11:12         ` Jean-Francois Moine
2011-07-21 10:43           ` Luiz Ramos
2011-07-21 11:27             ` Jean-Francois Moine [this message]

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=20110721132701.2a305d8e@tele \
    --to=moinejf@free.fr \
    --cc=linux-media@vger.kernel.org \
    --cc=lramos.prof@yahoo.com.br \
    /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.