All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [RFC PATCH 01/11] ALSA: implement MEDIA_IOC_DEVICE_INFO
Date: Fri, 07 Sep 2012 09:14:30 +0200	[thread overview]
Message-ID: <50499ED6.9070805@ladisch.de> (raw)
In-Reply-To: <20120907021309.GD6827@opensource.wolfsonmicro.com>

Mark Brown wrote:
> On Tue, Aug 28, 2012 at 12:29:33AM +0200, Clemens Ladisch wrote:
>> +config SND_MEDIA
>> +	bool "Media Controller API (EXPERIMENTAL)"
>> +	depends on EXPERIMENTAL
>> +	help
>> +	  Say Y here to enable the media controller API, which allows to
>> +	  retrieve the internal topology of sound devices.
>
> I think there's a general consensus these days that EXPERIMENTAL is
> pretty meaningless so we probably shouldn't bother with it.

Well, I couldn't claim this to be any less experimental than the
implementation in drivers/media/.  :)

> The text is also a bit confusing, it enables use of the media
> controller API for ALSA devices really.

It's in the ALSA menu.  I could put "ALSA" in the title if it helps.

> I have to say I'm also a bit surprised that there's no core framework
> for media controller and we're open coding ioctl() implementations here,

drivers/media/media-*.c exists, but I did not use that implementation
because someone expressed concern about it being too heavyweight ...

> I'd have thought there would at least be a way of enumerating all media
> controller devices in the system...

It appears userspace is supposed to check all /dev/media* devices.
(Using /dev/snd/controlC* is just a makeshift arrangement; I'll have to
reuse some part of the media device registration framework, or tell udev
to create symlinks.)


Regards,
Clemens

  reply	other threads:[~2012-09-07  7:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 22:28 [RFC PATCH 1/11] expose sound device topology information Clemens Ladisch
2012-08-27 22:29 ` [RFC PATCH 01/11] ALSA: implement MEDIA_IOC_DEVICE_INFO Clemens Ladisch
2012-09-07  2:13   ` Mark Brown
2012-09-07  7:14     ` Clemens Ladisch [this message]
2012-09-07 10:40       ` Takashi Iwai
2012-08-27 22:30 ` [RFC PATCH 02/11] ALSA: implement MEDIA_IOC_ENUM_ENTITIES Clemens Ladisch
2012-08-27 22:30 ` [RFC PATCH 03/11] ALSA: pcm: add ALSA PCM device entities Clemens Ladisch
2012-08-27 22:31 ` [RFC PATCH 04/11] ALSA: implement MEDIA_IOC_ENUM_LINKS (1) Clemens Ladisch
2012-08-27 22:31 ` [RFC PATCH 05/11] ALSA: implement MEDIA_IOC_ENUM_LINKS (2) Clemens Ladisch
2012-08-27 22:32 ` [RFC PATCH 06/11] ALSA: implement MEDIA_IOC_SETUP_LINK Clemens Ladisch
2012-08-27 22:33 ` [RFC PATCH 07/11] [media] media: add entity types for ALSA Clemens Ladisch
2012-08-27 22:33 ` [RFC PATCH 08/11] ALSA: usb-audio: implement card get_info callback Clemens Ladisch
2012-08-27 22:34 ` [RFC PATCH 09/11] ALSA: usb-audio: create PCM device entities Clemens Ladisch
2012-08-27 22:35 ` [RFC PATCH 10/11] ALSA: usb-audio: add terminal/unit entities and links Clemens Ladisch
2012-08-27 22:36 ` [RFC PATCH 11/11] ALSA: hda-intel: implement card get_info callback Clemens Ladisch
2012-09-04 15:56 ` [RFC PATCH 1/11] expose sound device topology information Takashi Iwai
2012-09-04 18:02   ` Clemens Ladisch

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=50499ED6.9070805@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --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 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.