public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean-Francois Moine <moinejf@free.fr>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: linux-media@vger.kernel.org, Max Thrun <bear24rw@gmail.com>
Subject: Re: [PATCH 05/11] ov534: Fix setting manual exposure
Date: Sun, 28 Feb 2010 20:42:12 +0100	[thread overview]
Message-ID: <20100228204212.0b78f1f9@tele> (raw)
In-Reply-To: <20100228195425.0be36259.ospite@studenti.unina.it>

On Sun, 28 Feb 2010 19:54:25 +0100
Antonio Ospite <ospite@studenti.unina.it> wrote:

> JF, the intent here is to cover all the range of values available in
> Auto Exposure mode too, doesn't this make sense to you?
> 
> I could set .maximum to 253 to limit the "UI" control precision but
> then I should use 2*value when setting the registers in order to
> cover the actual max value, this looks a little unclean.
> 
> Anyhow, let me know what you prefer, I have no strong feelings on
> that. If you want to save a byte, I'll agree.

Looking at the rare chip documents I got, I often saw internal control
values on 3 bytes (16 million values). Could anybody see the difference
between values v and (v+1)?

So, often, even when the internal controls are stored in only one byte,
the ms-win drivers propose only ranges as 0..30 or 0..100.

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

  reply	other threads:[~2010-02-28 19:41 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27 20:20 [PATCH 00/11] ov534: Fixes and updates Antonio Ospite
2010-02-27 20:20 ` [PATCH 01/11] ov534: Remove ambiguous controls Antonio Ospite
2010-02-27 20:20 ` [PATCH 02/11] ov534: Remove hue control Antonio Ospite
2010-02-27 20:20 ` [PATCH 03/11] ov534: Fix autogain control, enable it by default Antonio Ospite
2010-02-27 20:20 ` [PATCH 04/11] ov534: Add Auto Exposure Antonio Ospite
2010-02-27 20:20 ` [PATCH 05/11] ov534: Fix setting manual exposure Antonio Ospite
2010-02-28 18:38   ` Jean-Francois Moine
2010-02-28 18:54     ` Antonio Ospite
2010-02-28 19:42       ` Jean-Francois Moine [this message]
2010-03-01 11:10       ` Antonio Ospite
2010-03-01 11:53         ` [PATCH v2 05/11] ov534: Fix and document " Antonio Ospite
2010-02-27 20:20 ` [PATCH 06/11] ov534: Fix Auto White Balance control Antonio Ospite
2010-02-27 20:20 ` [PATCH 07/11] ov534: Fixes for sharpness control Antonio Ospite
2010-02-27 20:20 ` [PATCH 08/11] ov534: Fix unsetting hflip and vflip bits Antonio Ospite
2010-02-27 20:20 ` [PATCH 09/11] ov534: Cosmetics: fix indentation and hex digits Antonio Ospite
2010-02-28 18:46   ` Jean-Francois Moine
2010-02-28 19:11     ` Antonio Ospite
2010-03-01 11:54       ` [PATCH v2 " Antonio Ospite
2010-02-27 20:20 ` [PATCH 10/11] ov534: Add Powerline Frequency control Antonio Ospite
2010-02-28 18:49   ` Jean-Francois Moine
2010-02-28 19:18     ` Antonio Ospite
2010-02-28 19:55       ` Jean-Francois Moine
2010-03-02 11:26         ` M.Ebrahimi
2010-03-02 15:39           ` Antonio Ospite
     [not found]             ` <7b67a5ec1003020806x65164673ue699de2067bc4fb8@mail.gmail.com>
2010-03-03  2:27               ` M.Ebrahimi
     [not found]                 ` <7b67a5ec1003021830g13b2793eo4d681e4838ca2193@mail.gmail.com>
2010-03-03  2:41                   ` M.Ebrahimi
2010-03-03  8:00                 ` Antonio Ospite
2010-03-03  8:37                   ` Jean-Francois Moine
2010-03-03 10:57                     ` Antonio Ospite
2010-03-03 12:08                       ` Jean-Francois Moine
2010-03-04  4:55                   ` Jim Paris
2010-03-04  9:03                     ` Antonio Ospite
2010-03-04 20:14                       ` Jim Paris
     [not found]                         ` <7b67a5ec1003041222g25af69daq50fc62aeb8c85b96@mail.gmail.com>
2010-03-04 20:36                           ` Jim Paris
2010-03-05 16:18                         ` Antonio Ospite
2010-03-08 16:52                           ` [PATCH v2 " Antonio Ospite
2010-02-27 20:20 ` [PATCH 11/11] ov534: Update copyright info Antonio Ospite

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=20100228204212.0b78f1f9@tele \
    --to=moinejf@free.fr \
    --cc=bear24rw@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=ospite@studenti.unina.it \
    /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