All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [REANNOUNCE] Audio Mini Summit 2015, 8th October, Dublin
Date: Mon, 3 Aug 2015 08:51:28 +0530	[thread overview]
Message-ID: <20150803032128.GO29916@localhost> (raw)
In-Reply-To: <55BC772C.50801@metafoo.de>

On Sat, Aug 01, 2015 at 09:37:16AM +0200, Lars-Peter Clausen wrote:
> On 07/14/2015 05:03 PM, Mark Brown wrote:
> > [...]
> > 
> > and please follow up to this mail with any topics you'd like to see
> > raised so we can start collecting them (probably another Google doc will
> > be forthcoming for them).
> 
> Full media controller integration for both ALSA and ASoC. How this can be
> used to export topology information to userspace and how to for example
> attach a specific volume control to a specific media controller entity. And
> maybe also how to de-duplicate similar functionality between DAPM and media
> controller.
The recently merged topology core allows us to 'send' the complete topology
information for a component to kernel drivers.

So with this we now we have two additional choices:
- assuming all components use topology framework, we don't need to query, we
  use the topology information available in usermode. Some more support to
  parse topology binary installed and show as controls in alsa-lib might be
  required here
- do a reverse path, based on dapm and control info (driver will need to add
  code for linking the two) we add a new reverse API, which tells us the
  topology information from kernel

-- 
~Vinod

  reply	other threads:[~2015-08-03  3:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 15:03 [REANNOUNCE] Audio Mini Summit 2015, 8th October, Dublin Mark Brown
2015-07-14 16:04 ` Alexander E. Patrakov
2015-07-14 16:17   ` Mark Brown
2015-07-14 16:36     ` Alexander E. Patrakov
2015-07-14 17:05       ` Alexander E. Patrakov
2015-07-27 23:26   ` Pierre-Louis Bossart
2015-07-18 17:07 ` Vinod Koul
2015-09-10 21:35   ` Eric Laurent
2015-09-14 18:02     ` Mark Brown
2015-09-14 18:10       ` Eric Laurent
2015-07-21 11:29 ` Bard Liao
2015-07-27 23:05   ` Pierre-Louis Bossart
2015-08-03  3:15     ` Vinod Koul
2015-09-22  8:49       ` Arun Raghavan
2015-10-03 16:13         ` Takashi Iwai
2015-10-04 22:57           ` Mark Brown
2015-10-04 23:19             ` Mark Brown
2015-10-04  9:24         ` Arun Raghavan
2015-08-01  7:37 ` Lars-Peter Clausen
2015-08-03  3:21   ` Vinod Koul [this message]
2015-08-04 16:13     ` Mark Brown
2015-08-05  2:56       ` Vinod Koul
2015-08-05  9:39         ` Mark Brown
2015-08-03 19:11   ` Pierre-Louis Bossart
2015-08-04 16:03   ` Mark Brown
2015-08-04 18:50     ` Lars-Peter Clausen

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=20150803032128.GO29916@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.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.