Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	"Koul, Vinod" <vinod.koul@intel.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [RFC 0/4] ASoC DSP topology
Date: Mon, 20 Apr 2015 22:40:32 +0100	[thread overview]
Message-ID: <20150420214032.GV14892@sirena.org.uk> (raw)
In-Reply-To: <1429217285.7100.18.camel@loki>


[-- Attachment #1.1: Type: text/plain, Size: 658 bytes --]

On Thu, Apr 16, 2015 at 09:48:05PM +0100, Liam Girdwood wrote:
> It's been about 2 years since posting V1 of the ASoC dynamic firmware patches
> and a lot has changed since then ...

:)

> Kernel. The kernel core reads in the topology data and builds the driver
> capabilities and audio topology based on this data. This includes building
> the DAPM graph, setting PCM and DAI capabilities, registering kcontrols and
> registering DAPM widgets.

I think the topology code itself looks good, I'll take another pass over
it though since there's a lot to get through.  The main thing is to make
sure the ABI makes sense though - we can fix up the kernel later.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2015-04-20 21:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 20:48 [RFC 0/4] ASoC DSP topology Liam Girdwood
2015-04-20 21:40 ` Mark Brown [this message]
2015-04-21  6:58 ` Peter Ujfalusi
2015-04-21  9:28   ` Mark Brown
2015-04-21 10:03     ` Liam Girdwood
2015-04-21 12:30     ` Peter Ujfalusi
2015-04-21 15:23       ` Liam Girdwood
2015-04-21 16:39         ` Mark Brown
2015-04-22  4:10           ` Vinod Koul

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=20150420214032.GV14892@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@intel.com \
    /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