All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: RFC: V4L2 API and radio devices with multiple tuners
Date: Sat, 19 May 2012 21:04:47 +0200	[thread overview]
Message-ID: <4FB7EECF.1000402@redhat.com> (raw)
In-Reply-To: <201205192030.53616.linux@rainbow-software.org>

Hi,

On 05/19/2012 08:30 PM, Ondrej Zary wrote:
> On Saturday 19 May 2012 20:20:57 Hans de Goede wrote:
>> Hi Hans et all,
>>
>> 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.
>
> When working on tea575x driver, I thought that it would be nice to implement
> AM. But found that none of my cards with TEA575x has implemented the AM part.

I have a tea5757 device which does implement the AM part, the Griffin radioSHARK,
and I'm working on a driver for it now, including some mods to the existing
tea575x driver, this is one of the reasons I CC-ed you on this RFC.

If you would like to get a radioSHARK yourself, you can get one here:
http://www.ebay.com/itm/Griffin-RadioShark-PC-MAC-AM-FM-Desktop-Radio-/140547171120?pt=LH_DefaultDomain_0&hash=item20b943a330

Do you have any comments on my proposal how to deal with these
devices API wise?

> The components required to receive AM radio (according to the chip datasheet)
> are missing.

Right I already expected that my WIP patch to add AM support to the tea575x driver
adds a has_am boolean and only makes AM available if that is set.

I hope to post a set of tea575x patches this evening, most are non controversial
so unless someone (ie you) yells stop I'm going to include them in my next pull
request to Mauro for 3.5 (which will hopefully happen tomorrow).

Unless some quick consensus can be reached on how to deal with the radio
device with dual mode tuner API issue I'll leave out the AM patch from
my pullreq.

Thanks & Regards,

Hans


  reply	other threads:[~2012-05-19 19:00 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 [this message]
2012-05-19 18:36 ` Antti Palosaari
2012-05-22 16:26   ` Rémi Denis-Courmont
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=4FB7EECF.1000402@redhat.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.