From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH 0/3] conf: Add vendor tuples in conf
Date: Tue, 23 Aug 2016 09:26:50 +0530 [thread overview]
Message-ID: <20160823035650.GU2890@localhost> (raw)
In-Reply-To: <s5hfupxf0r5.wl-tiwai@suse.de>
On Mon, Aug 22, 2016 at 02:26:22PM +0200, Takashi Iwai wrote:
> On Fri, 12 Aug 2016 09:00:14 +0200,
> Vinod Koul wrote:
> >
> > Topology changes in alsa-lib allow driver data for modules to be be passed
> > in topology conf file using tuples. These changes allow private data to
> > represented by tuples of type UUID, byte, short, word and strings.
> >
> > This patch series adds changes to :
> > - include tuple and token list in the conf file
> > to define module private data.
> > - Private data blobs for modules are no longer required. So, remove the
> > binary blobs and the tool used to generate the blobs.
> > - Then add bxt conf file which is based on tuples
> >
> > Takashi,
> > This should be merged after the kernel changes are merged.
> >
> > Shreyas NC (3):
> > conf: sklrt286: define module private data through tuples in skylake
> > conf: sklrt286: Remove tool to generate private data blobs
> > conf: bxtrt298: Add topology conf file for bxt
>
> Did you submit all patches? I've seen only this cover letter.
> In anyway, please resubmit.
Ah not sure, how. I will send again now
--
~Vinod
prev parent reply other threads:[~2016-08-23 3:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 7:00 [PATCH 0/3] conf: Add vendor tuples in conf Vinod Koul
2016-08-22 12:26 ` Takashi Iwai
2016-08-23 3:56 ` Vinod Koul [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=20160823035650.GU2890@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).