All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eliot Blennerhassett <linux@audioscience.com>
To: alsa-devel@alsa-project.org
Subject: Control interconnection information API?
Date: Thu, 01 Jan 2009 12:01:47 +1300	[thread overview]
Message-ID: <495BF9DB.2060202@audioscience.com> (raw)

New Year's Greetings,


something that seems to be lacking in the ALSA API, or at least the way
of describing controls (by name only), is any concept of the
connectivity between the various controls and the codecs and output
terminals.

One use for such information is to build a GUI that shows this
connectivity (instead of the current bucket'o'controls approach).

Now there are a couple of special cases:

* HDA driver exports the codec widget information via a proc file,
allowing the codecgraph tool to visualise the connections.
Widgets have numeric IDs and list the IDs of widgets that connect to
their inputs.

* ASoC DAPM (which I (not being an ASoC developer or user) have mostly
been skimming over in this list).

Reading this
http://www.mjmwired.net/kernel/Documentation/sound/alsa/soc/dapm.txt
3. Codec Widget Interconnections. I can see that there are lists of
connections.  I'm not sure if these are visible to userspace via any API?


So:
Can either of these schemes be generalised to all ALSA drivers?
Is there some other way to reveal the information (Connections TLV, new
API etc?)
Does anybody else thing this is worth pursuing, or is it just me?


regards

--
Eliot Blennerhassett
AudioScience Inc

             reply	other threads:[~2008-12-31 23:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-31 23:01 Eliot Blennerhassett [this message]
2009-01-01 11:43 ` Control interconnection information API? Mark Brown

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=495BF9DB.2060202@audioscience.com \
    --to=linux@audioscience.com \
    --cc=alsa-devel@alsa-project.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.