From: Vinod Koul <vkoul@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
tiwai@suse.de, broonie@kernel.org, gregkh@linuxfoundation.org,
jank@cadence.com, srinivas.kandagatla@linaro.org,
rander.wang@linux.intel.com, ranjani.sridharan@linux.intel.com,
hui.wang@canonical.com, pierre-louis.bossart@linux.intel.com,
sanyog.r.kale@intel.com, mengdong.lin@intel.com,
bard.liao@intel.com
Subject: Re: [PATCH v2 0/3] ASoC: Add sdw stream operations to dailink ops.
Date: Fri, 4 Sep 2020 14:49:50 +0530 [thread overview]
Message-ID: <20200904091950.GX2639@vkoul-mobl> (raw)
In-Reply-To: <20200903204650.31098-1-yung-chuan.liao@linux.intel.com>
On 04-09-20, 04:46, Bard Liao wrote:
> Sdw stream operation APIs can be called once per stream. Move these
> operations to dailink ops. The linked series is "soundwire: Remove sdw
> stream operations from Intel soundwire dai".
>
> Pierre-Louis Bossart (3):
> ASoC: soc-dai: clarify return value for get_sdw_stream()
> ASOC: Intel: sof_sdw: add dailink .trigger callback
> ASOC: Intel: sof_sdw: add dailink .prepare and .hw_free callback
s/ASOC/ASoC
with that:
Reviewed-by: Vinod Koul <vkoul@kernel.org>
>
> include/sound/soc-dai.h | 3 +-
> sound/soc/intel/boards/sof_sdw.c | 81 ++++++++++++++++++++++++++++++++
> 2 files changed, 83 insertions(+), 1 deletion(-)
>
> --
> 2.17.1
--
~Vinod
prev parent reply other threads:[~2020-09-04 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 20:46 [PATCH v2 0/3] ASoC: Add sdw stream operations to dailink ops Bard Liao
2020-09-03 20:46 ` [PATCH v2 1/3] ASoC: soc-dai: clarify return value for get_sdw_stream() Bard Liao
2020-09-03 20:46 ` [PATCH v2 2/3] ASOC: Intel: sof_sdw: add dailink .trigger callback Bard Liao
2020-09-03 20:46 ` [PATCH v2 3/3] ASOC: Intel: sof_sdw: add dailink .prepare and .hw_free callback Bard Liao
2020-09-04 9:19 ` 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=20200904091950.GX2639@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mengdong.lin@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@linux.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).