From: Takashi Iwai <tiwai@suse.de>
To: fuweix.tang@intel.com
Cc: liam.r.girdwood@linux.intel.com, mengdong.lin@intel.com,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/4] topology: Support using "index" to group objects when generating binary for kernel
Date: Fri, 21 Apr 2017 12:58:40 +0200 [thread overview]
Message-ID: <s5hmvbakowv.wl-tiwai@suse.de> (raw)
In-Reply-To: <cover.1492065639.git.fuweix.tang@intel.com>
On Thu, 13 Apr 2017 08:52:43 +0200,
fuweix.tang@intel.com wrote:
>
> From: Fuwei Tang <fuweix.tang@intel.com>
>
> The index value of an topology object can be used to group objects for different
> use cases. And so the audio kernel driver can ask topology core to load all
> objects of the specified index value(use case). The function is already supported
> in kernel.
> So in the user space, for topology objects of the same type but with different
> index values, they should be written into different blocks in the binary for
> kernel. The index value is stored in the block header.
>
> Fuwei Tang (4):
> topology: Insert new element based on its index value
> topology: Remove code parsing index value in paring each object
> topology: Look up references for an object based on its index
> topology: Group elements with the same index value into a block
Applied these four patches now. Thanks.
Takashi
prev parent reply other threads:[~2017-04-21 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 6:52 [PATCH 0/4] topology: Support using "index" to group objects when generating binary for kernel fuweix.tang
2017-04-13 6:52 ` [PATCH 1/4] topology: Insert new element based on its index value fuweix.tang
2017-04-13 6:52 ` [PATCH 2/4] topology: Remove code parsing index value in paring each object fuweix.tang
2017-04-13 6:52 ` [PATCH 3/4] topology: Look up references for an object based on its index fuweix.tang
2017-04-13 6:52 ` [PATCH 4/4] topology: Group elements with the same index value into a block fuweix.tang
2017-04-21 10:58 ` Takashi Iwai [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=s5hmvbakowv.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=fuweix.tang@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mengdong.lin@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.