From: Mengdong Lin <mengdong.lin@linux.intel.com>
To: alsa-devel@alsa-project.org, broonie@kernel.org
Cc: vinod.koul@intel.com, hardik.t.shah@intel.com,
liam.r.girdwood@linux.intel.com, mengdong.lin@intel.com,
jeeja.kp@intel.com, subhransu.s.prusty@intel.com
Subject: Re: [PATCH v3 0/2] ASoC: topology: Add support for FE DAI & DAI links
Date: Tue, 16 Feb 2016 14:17:20 +0800 [thread overview]
Message-ID: <56C2BEF0.4090106@linux.intel.com> (raw)
In-Reply-To: <cover.1455599774.git.mengdong.lin@linux.intel.com>
Please overlook this v3 series, since the v2 were just applied.
I've sent out a separate patch to fix setting of a stream's rates:
[PATCH] ASoC: topology: Fix setting of stream rates, rate_min and rate_max
On 02/16/2016 01:39 PM, mengdong.lin@linux.intel.com wrote:
> From: Mengdong Lin <mengdong.lin@linux.intel.com>
>
> This series allows topology to create FE DAI and DAI links from the PCM
> topology objects defined by the user space.
>
> History:
> v2: Remove first 2 patches in v1 that were accepted.
> Add Ack by Takashi to patch 'ALSA: pcm: Add snd_pcm_rate_range_to_bits()'
> and add his comments on the function's assumption to c file.
>
>
> v3: remove 1st patch in v2 that was accepted.
> Revise setting of a stream's rates/rate_min/rate_max as Lars suggested.
>
> Mengdong Lin (2):
> ASoC: topology: Add FE DAIs dynamically
> ASoC: topology: Add FE DAI links dynamically
>
> include/sound/soc-topology.h | 21 +++--
> include/sound/soc.h | 2 +-
> sound/soc/soc-topology.c | 195 ++++++++++++++++++++++++++++++++++---------
> 3 files changed, 165 insertions(+), 53 deletions(-)
>
prev parent reply other threads:[~2016-02-16 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 5:39 [PATCH v3 0/2] ASoC: topology: Add support for FE DAI & DAI links mengdong.lin
2016-02-16 5:42 ` [PATCH v3 1/2] ASoC: topology: Add FE DAIs dynamically mengdong.lin
2016-02-16 5:43 ` [PATCH v3 2/2] ASoC: topology: Add FE DAI links dynamically mengdong.lin
2016-02-16 6:17 ` Mengdong Lin [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=56C2BEF0.4090106@linux.intel.com \
--to=mengdong.lin@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=hardik.t.shah@intel.com \
--cc=jeeja.kp@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mengdong.lin@intel.com \
--cc=subhransu.s.prusty@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).