From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mark Brown <broonie@linaro.org>
Cc: Marek Vasut <marex@denx.de>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: pcm: Require both CODEC and CPU support when declaring stream caps
Date: Mon, 03 Jun 2013 09:47:31 +0100 [thread overview]
Message-ID: <1370249251.2476.2.camel@loki> (raw)
In-Reply-To: <1370124976-25047-1-git-send-email-broonie@linaro.org>
On Sat, 2013-06-01 at 23:16 +0100, Mark Brown wrote:
> When declaring playback and capture capabilities check for both CODEC
> side and CPU side support rather than only checking for CODEC side
> support. While it is unusual some CPUs do have unidirectional DAIs.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
Acked-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
prev parent reply other threads:[~2013-06-03 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 22:16 [PATCH] ASoC: pcm: Require both CODEC and CPU support when declaring stream caps Mark Brown
2013-06-01 23:01 ` Fabio Estevam
2013-06-02 14:45 ` Fabio Estevam
2013-06-03 8:56 ` Mark Brown
2013-06-03 8:47 ` Liam Girdwood [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=1370249251.2476.2.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=broonie@linaro.org \
--cc=festevam@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=marex@denx.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).