From: Jean-Francois Moine <moinejf@free.fr>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH] gspca - ov534: Fix the light frequency filter
Date: Fri, 23 Nov 2012 19:12:32 +0100 [thread overview]
Message-ID: <20121123191232.7ed9c546@armhf> (raw)
In-Reply-To: <20121123180909.021c55a8c3795329836c42b7@studenti.unina.it>
On Fri, 23 Nov 2012 18:09:09 +0100
Antonio Ospite <ospite@studenti.unina.it> wrote:
> On Thu, 22 Nov 2012 12:46:52 +0100
[snip]
> Jean-Francois Moine <moinejf@free.fr> wrote:
> > This patch was done thanks to the documentation of the right
> > OmniVision sensors.
>
> In the datasheet I have for ov772x, bit[6] of register 0x13 is described
> as:
>
> Bit[6]: AEC - Step size limit
> 0: Step size is limited to vertical blank
> 1: Unlimited step size
Right, but I don't use the bit 6, it is the bit 5:
> > + sccb_reg_write(gspca_dev, 0x13, /* auto */
> > + sccb_reg_read(gspca_dev, 0x13) | 0x20);
which is described as:
Bit[5]: Banding filter ON/OFF
> And the patch makes Light Frequency _NOT_ work with the PS3 eye (based
> on ov772x).
>
> What does the ov767x datasheet say?
Quite the same thing:
Bit[5]: Banding filter ON/OFF - In order to turn ON the banding
filter, BD50ST (0x9D) or BD60ST (0x9E) must be set to a
non-zero value.
0: OFF
1: ON
(the registers 9d and 9e are non zero for the ov767x in ov534.c)
> Maybe we should use the new values only when
> sd->sensor == SENSOR_OV767x
>
> What sensor does Alexander's webcam use?
He has exactly the same webcam as yours: 1415:2000 (ps eye) with
sensor ov772x.
> > Note: The light frequency filter is either off or automatic.
> > The application will see either off or "50Hz" only.
> >
> > Tested-by: alexander calderon <fabianp902@gmail.com>
> > Signed-off-by: Jean-François Moine <moinejf@free.fr>
> >
> > --- a/drivers/media/usb/gspca/ov534.c
> > +++ b/drivers/media/usb/gspca/ov534.c
> > @@ -1038,13 +1038,12 @@
> > {
> > struct sd *sd = (struct sd *) gspca_dev;
> >
>
> drivers/media/usb/gspca/ov534.c: In function ‘setlightfreq’:
> drivers/media/usb/gspca/ov534.c:1039:13: warning: unused variable ‘sd’ [-Wunused-variable]
Thanks.
Well, here is one of the last message I received from Alexander (in
fact, his first name is Fabian):
> Thanks for all your help, it is very kind of you, I used the code below,the
> 60 Hz filter appear to work even at 100fps, but when I used 125 fps it
> didnt work :( , i guess it is something of detection speed. If you have any
> other idea I'll be very thankful.
>
> Sincerely Fabian Calderon
So, how may we advance?
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2012-11-23 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 11:46 [PATCH] gspca - ov534: Fix the light frequency filter Jean-Francois Moine
2012-11-23 17:09 ` Antonio Ospite
2012-11-23 18:12 ` Jean-Francois Moine [this message]
2012-11-26 13:08 ` Antonio Ospite
2012-11-26 15:23 ` Jean-Francois Moine
2012-11-26 17:12 ` Antonio Ospite
2012-11-26 17:51 ` Jean-Francois Moine
2012-11-29 9:25 ` Hans de Goede
2012-11-29 22:14 ` Antonio Ospite
-- strict thread matches above, loose matches on Subject: below --
2012-11-22 11:33 Jean-Francois Moine
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=20121123191232.7ed9c546@armhf \
--to=moinejf@free.fr \
--cc=hdegoede@redhat.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