From: Ondrej Zary <linux@rainbow-software.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH] tea575x: fix HW seek
Date: Wed, 22 Feb 2012 09:35:28 +0100 [thread overview]
Message-ID: <201202220935.29155.linux@rainbow-software.org> (raw)
In-Reply-To: <201202211044.14925.hverkuil@xs4all.nl>
On Tuesday 21 February 2012, Hans Verkuil wrote:
> On Saturday, February 18, 2012 17:45:45 Ondrej Zary wrote:
> > Fix HW seek in TEA575x to work properly:
> > - a delay must be present after search start and before first register
> > read or the seek does weird things
> > - when the search stops, the new frequency is not available immediately,
> > we must wait until it appears in the register (fortunately, we can clear
> > the frequency bits when starting the search as it starts at the frequency
> > currently set, not from the value written)
> > - sometimes, seek remains on the current frequency (or moves only a
> > little), so repeat it until it moves by at least 50 kHz
> >
> > Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
> >
> > --- a/sound/i2c/other/tea575x-tuner.c
> > +++ b/sound/i2c/other/tea575x-tuner.c
> > @@ -89,7 +89,7 @@ static void snd_tea575x_write(struct snd_tea575x *tea,
> > unsigned int val) tea->ops->set_pins(tea, 0);
> > }
> >
> > -static unsigned int snd_tea575x_read(struct snd_tea575x *tea)
> > +static u32 snd_tea575x_read(struct snd_tea575x *tea)
> > {
> > u16 l, rdata;
> > u32 data = 0;
> > @@ -120,6 +120,27 @@ static unsigned int snd_tea575x_read(struct
> > snd_tea575x *tea) return data;
> > }
> >
> > +static void snd_tea575x_get_freq(struct snd_tea575x *tea)
> > +{
> > + u32 freq = snd_tea575x_read(tea) & TEA575X_BIT_FREQ_MASK;
> > +
> > + if (freq == 0) {
> > + tea->freq = 0;
>
> Wouldn't it be better to return -EBUSY in this case? VIDIOC_G_FREQUENCY
> should not return frequencies outside the valid frequency range. In this
> case returning -EBUSY seems to make more sense to me.
The device returns zero frequency when the scan fails to find a frequency.
This is not an error, just an indication that "nothing" is tuned. So maybe we
can return some bogus frequency in vidioc_g_frequency (like FREQ_LO) in this
case (don't know if -EBUSY will break anything). But HW seek should get the
real one (i.e. zero when it's there).
> I'm proposing adding this patch:
>
> diff --git a/sound/i2c/other/tea575x-tuner.c
> b/sound/i2c/other/tea575x-tuner.c index 474bb81..02da22f 100644
> --- a/sound/i2c/other/tea575x-tuner.c
> +++ b/sound/i2c/other/tea575x-tuner.c
> @@ -120,14 +120,12 @@ static u32 snd_tea575x_read(struct snd_tea575x *tea)
> return data;
> }
>
> -static void snd_tea575x_get_freq(struct snd_tea575x *tea)
> +static int snd_tea575x_get_freq(struct snd_tea575x *tea)
> {
> u32 freq = snd_tea575x_read(tea) & TEA575X_BIT_FREQ_MASK;
>
> - if (freq == 0) {
> - tea->freq = 0;
> - return;
> - }
> + if (freq == 0)
> + return -EBUSY;
>
> /* freq *= 12.5 */
> freq *= 125;
> @@ -139,6 +137,7 @@ static void snd_tea575x_get_freq(struct snd_tea575x
> *tea) freq -= TEA575X_FMIF;
>
> tea->freq = clamp(freq * 16, FREQ_LO, FREQ_HI); /* from kHz */
> + return 0;
> }
>
> static void snd_tea575x_set_freq(struct snd_tea575x *tea)
> @@ -220,14 +219,15 @@ static int vidioc_g_frequency(struct file *file, void
> *priv, struct v4l2_frequency *f)
> {
> struct snd_tea575x *tea = video_drvdata(file);
> + int ret = 0;
>
> if (f->tuner != 0)
> return -EINVAL;
> f->type = V4L2_TUNER_RADIO;
> if (!tea->cannot_read_data)
> - snd_tea575x_get_freq(tea);
> + ret = snd_tea575x_get_freq(tea);
> f->frequency = tea->freq;
> - return 0;
> + return ret;
> }
>
> static int vidioc_s_frequency(struct file *file, void *priv,
> @@ -250,11 +250,14 @@ static int vidioc_s_hw_freq_seek(struct file *file,
> void *fh, struct snd_tea575x *tea = video_drvdata(file);
> int i, old_freq;
> unsigned long timeout;
> + int ret;
>
> if (tea->cannot_read_data)
> return -ENOTTY;
>
> - snd_tea575x_get_freq(tea);
> + ret = snd_tea575x_get_freq(tea);
> + if (ret)
> + return ret;
> old_freq = tea->freq;
> /* clear the frequency, HW will fill it in */
> tea->val &= ~TEA575X_BIT_FREQ_MASK;
> @@ -278,8 +281,8 @@ static int vidioc_s_hw_freq_seek(struct file *file,
> void *fh, /* Found a frequency, wait until it can be read */
> for (i = 0; i < 100; i++) {
> msleep(10);
> - snd_tea575x_get_freq(tea);
> - if (tea->freq != 0) /* available */
> + ret = snd_tea575x_get_freq(tea);
> + if (ret == 0) /* available */
> break;
> }
> /* if we moved by less than 50 kHz, continue seeking */
>
> If you are OK with this, then I'll put everything together and make a final
> pull request.
>
> Regards,
>
> Hans
--
Ondrej Zary
next prev parent reply other threads:[~2012-02-22 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-18 16:45 [PATCH] tea575x: fix HW seek Ondrej Zary
2012-02-21 9:44 ` Hans Verkuil
2012-02-22 8:35 ` Ondrej Zary [this message]
2012-02-24 9:00 ` Hans Verkuil
2012-02-26 21:02 ` Ondrej Zary
2012-02-27 8:42 ` Hans Verkuil
2012-02-27 18:11 ` Ondrej Zary
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=201202220935.29155.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=alsa-devel@alsa-project.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
/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).