linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: RFC: Core + Radio profile
Date: Wed, 22 Aug 2012 11:47:49 +0200	[thread overview]
Message-ID: <5034AAC5.4050306@redhat.com> (raw)
In-Reply-To: <201208221140.25656.hverkuil@xs4all.nl>

Hi,

On 08/22/2012 11:40 AM, Hans Verkuil wrote:
> Hi all!
>

<Snip>

> While writing down these profiles I noticed one thing that was very much
> missing for radio devices: there is no capability bit to tell the application
> whether there is an associated ALSA device or whether the audio goes through
> a line-in/out. Personally I think that this should be fixed.

The question with generic tuner drivers like the tea57XX series is do we always
know this ?

One could argue to proper way to find this out for applications is by looking
at the device topology, either through the media controller framework, or
through sysfs. This is for example what xawtv currently does. We need a better
library to handle this, which also hides from the user whether the media controller
or sysfs is used.

 > Comments are welcome!

Looks good!

Regards,

Hans

  reply	other threads:[~2012-08-22  9:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22  9:40 RFC: Core + Radio profile Hans Verkuil
2012-08-22  9:47 ` Hans de Goede [this message]
2012-08-22 10:11 ` Hans Verkuil
2012-08-22 13:42   ` Mauro Carvalho Chehab
2012-08-22 15:19     ` Mike Isely
2012-08-22 18:09       ` Mauro Carvalho Chehab
2012-08-23 11:12         ` Andy Walls
2012-08-24 12:31     ` Hans Verkuil
2012-08-24 14:51       ` Mauro Carvalho Chehab
2012-08-24 15:35         ` Hans Verkuil
2012-08-26 22:56       ` Andy Walls
2012-08-25  0:37 ` Andy Walls
2012-08-25  7:21   ` Hans Verkuil
2012-08-26 22:15     ` Andy Walls

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=5034AAC5.4050306@redhat.com \
    --to=hdegoede@redhat.com \
    --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).