linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: "Takashi Iwai" <tiwai@suse.de>,
	jirislaby@gmail.com, alsa-devel@alsa-project.org,
	"Kernel development list" <linux-kernel@vger.kernel.org>,
	linux-media@vger.kernel.org
Subject: Re: [RFC PATCH 1/3] tea575x-tuner: various improvements
Date: Tue, 29 Mar 2011 21:25:55 +0200	[thread overview]
Message-ID: <201103292125.58561.linux@rainbow-software.org> (raw)
In-Reply-To: <201103261119.31897.hverkuil@xs4all.nl>

On Saturday 26 March 2011 11:19:31 Hans Verkuil wrote:
> On Friday, March 25, 2011 22:40:12 Ondrej Zary wrote:
> > On Tuesday 22 March 2011 20:02:30 Hans Verkuil wrote:
> > > BTW, can you run the v4l2-compliance utility for the two boards that
> > > use this radio tuner?
> > >
> > > This utility is part of the v4l-utils repository
> > > (http://git.linuxtv.org/v4l-utils.git).
> > >
> > > Run as 'v4l2-compliance -r /dev/radioX -v2'.
> > >
> > > I'm sure there will be some errors/warnings (warnings regarding
> > > G/S_PRIORITY are to be expected). But I can use it to make a patch for
> > > 2.6.40 that fixes any issues.
> >
> > The output is the same for both fm801 and es1968 (see below). Seems that
> > there are 4 errors:
> >  1. multiple-open does not work
> >  2. something bad with s_frequency
> >  3. input functions are present
> >  4. no extended controls
>
> Thanks for testing! Some comments are below...
>
> > Running on 2.6.38
> >
> > Driver Info:
> > 	Driver name   : tea575x-tuner
> > 	Card type     : TEA5757
> > 	Bus info      : PCI
> > 	Driver version: 0.0.2
> > 	Capabilities  : 0x00050000
> > 		Tuner
> > 		Radio
> >
> > Compliance test for device /dev/radio0 (not using libv4l2):
> >
> > Required ioctls:
> > 	test VIDIOC_QUERYCAP: OK
> >
> > Allow for multiple opens:
> > 	test second radio open: FAIL
>
> I will fix this. Once 2.6.39-rc1 is released I can make a patch fixing
> this.
>
> > Debug ioctls:
> > 	test VIDIOC_DBG_G_CHIP_IDENT: Not Supported
> > 	test VIDIOC_DBG_G/S_REGISTER: Not Supported
> > 	test VIDIOC_LOG_STATUS: Not Supported
> >
> > Input ioctls:
> > 	test VIDIOC_G/S_TUNER: OK
> > 		fail: set rangehigh+1 frequency did not return EINVAL
> > 	test VIDIOC_G/S_FREQUENCY: FAIL
>
> Hmm, S_FREQUENCY apparently fails to check for valid frequency values.
> Can you take a quick look at the code?

The driver code is OK. But there is a bug in v4l2-test-input-output.cpp at 
line 214:
if (ret)
	return fail("set rangehigh+1 frequency did not return EINVAL\n");

There should be "if (ret != EINVAL)" instead of "if (ret)".

-- 
Ondrej Zary

  reply	other threads:[~2011-03-29 19:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 18:19 radio-maestro broken (conflicts with snd-es1968) Ondrej Zary
2011-03-12 18:52 ` Hans Verkuil
2011-03-14  9:53   ` [alsa-devel] " Takashi Iwai
2011-03-14  9:59     ` Hans Verkuil
2011-03-14 10:08       ` Takashi Iwai
2011-03-14 10:28       ` Ondrej Zary
2011-03-14 10:29         ` Takashi Iwai
2011-03-14 11:57         ` Hans Verkuil
2011-03-19 15:32           ` [RFC PATCH 1/3] tea575x-tuner: various improvements Ondrej Zary
2011-03-21 11:48             ` Takashi Iwai
2011-03-22 18:39               ` Mauro Carvalho Chehab
2011-03-22 19:02             ` Hans Verkuil
2011-03-25 21:40               ` Ondrej Zary
2011-03-26 10:19                 ` Hans Verkuil
2011-03-29 19:25                   ` Ondrej Zary [this message]
2011-03-29 19:39                     ` Hans Verkuil
2011-03-19 15:33           ` [RFC PATCH 2/3] tea575x-tuner: remove dev_nr Ondrej Zary
2011-03-19 15:33           ` [RFC PATCH 3/3] es1968: add radio (tea575x tuner) support Ondrej Zary
2011-03-19 16:23           ` [RFC PATCH 4/3] remove radio-maestro Ondrej Zary
2011-03-22 18:44             ` Mauro Carvalho Chehab
2011-03-23  7:13               ` Takashi Iwai
2011-03-22 19:03             ` Hans Verkuil
2011-03-14  9:46 ` [alsa-devel] radio-maestro broken (conflicts with snd-es1968) Takashi Iwai

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=201103292125.58561.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=hverkuil@xs4all.nl \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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).