From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>,
"Lin, Mengdong" <mengdong.lin@intel.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
"Koul, Vinod" <vinod.koul@intel.com>
Subject: Re: [RFC] File format for topology data
Date: Wed, 22 Apr 2015 19:44:03 +0100 [thread overview]
Message-ID: <20150422184403.GA22845@sirena.org.uk> (raw)
In-Reply-To: <1429621606.3793.37.camel@loki>
[-- Attachment #1.1: Type: text/plain, Size: 595 bytes --]
On Tue, Apr 21, 2015 at 02:06:46PM +0100, Liam Girdwood wrote:
> I've pasted below the topology data for the broadwell firmware using the
> text file format being used by UCM. Using the UCM format allows to to
> share parser code and allows us to also have UCM define topology data.
>
> I've not yet completed the byte or enum controls but the rest of the
> data is there for comments. I've also included the recent channel
> changes suggested in the UAPI header comments.
Just to check, this is the input format which will be compiled into the
topology files loaded by the kernel?
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-04-22 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 13:06 [RFC] File format for topology data Liam Girdwood
2015-04-22 15:58 ` Vinod Koul
2015-04-23 1:11 ` Liam Girdwood
2015-04-23 3:42 ` Vinod Koul
2015-04-22 18:44 ` Mark Brown [this message]
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=20150422184403.GA22845@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mengdong.lin@intel.com \
--cc=peter.ujfalusi@ti.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 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.