From: "Rémi Denis-Courmont" <remi@remlab.net>
To: Antti Palosaari <crope@iki.fi>
Cc: Hans de Goede <hdegoede@redhat.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Ondrej Zary <linux@rainbow-software.org>
Subject: Re: RFC: V4L2 API and radio devices with multiple tuners
Date: Tue, 22 May 2012 19:26:37 +0300 [thread overview]
Message-ID: <201205221926.38970.remi@remlab.net> (raw)
In-Reply-To: <4FB7E827.7070701@iki.fi>
Le samedi 19 mai 2012 21:36:23 Antti Palosaari, vous avez écrit :
> On 19.05.2012 21:20, Hans de Goede wrote:
> > Currently the V4L2 API does not allow for radio devices with more then 1
> > tuner,
> > which is a bit of a historical oversight, since many radio devices have 2
> > tuners/demodulators 1 for FM and one for AM. Trying to model this as 1
> > tuner
> > really does not work well, as they have 2 completely separate frequency
> > bands
> > they handle, as well as different properties (the FM part usually is
> > stereo capable, the AM part is not).
> >
> > It is important to realize here that usually the AM/FM tuners are part
> > of 1 chip, and often have only 1 frequency register which is used in
> > both AM/FM modes. IOW it more or less is one tuner, but with 2 modes,
> > and from a V4L2 API pov these modes are best modeled as 2 tuners.
> > This is at least true for the radio-cadet card and the tea575x,
> > which are the only 2 AM capable radio devices we currently know about.
>
> For DVB API we changed just opposite direction - from multi-frontend to
> single-frontend. I think one device per one standard is good choice.
If I understand Hans correctly, he suggests to use two tuners on a *single*
radio device node, much like a single video device nodes can have multiple
video inputs. So I think you agree with Hans, and so do I.
--
Rémi Denis-Courmont
http://www.remlab.net/
http://fi.linkedin.com/in/remidenis
next prev parent reply other threads:[~2012-05-22 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-19 18:20 RFC: V4L2 API and radio devices with multiple tuners Hans de Goede
2012-05-19 18:30 ` Ondrej Zary
2012-05-19 19:04 ` Hans de Goede
2012-05-19 18:36 ` Antti Palosaari
2012-05-22 16:26 ` Rémi Denis-Courmont [this message]
2012-05-22 20:45 ` Hans de Goede
2012-05-22 20:51 ` Hans Verkuil
2012-05-24 14:46 ` Antti Palosaari
2012-05-20 10:23 ` Hans Verkuil
2012-05-20 11:50 ` Hans de Goede
2012-05-20 14:34 ` Hans Verkuil
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=201205221926.38970.remi@remlab.net \
--to=remi@remlab.net \
--cc=crope@iki.fi \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=linux@rainbow-software.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).