From: Mark Brown <broonie@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: alsa-devel@alsa-project.org,
Stephan Gerhold <stephan@gerhold.net>,
Liam Girdwood <lgirdwood@gmail.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-kernel@vger.kernel.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
zhangn1985@outlook.com, linux-amlogic@lists.infradead.org
Subject: Re: [PATCH] ASoC: core: restore dpcm flags semantics
Date: Fri, 31 Jul 2020 18:42:07 +0100 [thread overview]
Message-ID: <20200731174207.GC4510@sirena.org.uk> (raw)
In-Reply-To: <1j7duj98wk.fsf@starbuckisacylon.baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
On Fri, Jul 31, 2020 at 02:16:43PM +0200, Jerome Brunet wrote:
> One last thing I'd like to understand. Is this behavior of throwing an
> error going to applied to the non-DPCM case as well ? so at least thing
> are consistent between both cases ?
> IOW:
> * An error is now throw if dpcm_capture is set on the link and the CPU
> DAI support playback_only
We should definitely complain about that.
> * on non-DPCM links, will an error be thrown as well if playback_only
> is not set and the CPU on the link happen to not support capture ?
I think we should move towards not needing to do that for DPCM.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-31 17:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 18:05 [PATCH] ASoC: core: use less strict tests for dailink capabilities Pierre-Louis Bossart
2020-07-24 8:31 ` Jerome Brunet
2020-07-24 19:05 ` Pierre-Louis Bossart
2020-07-27 9:42 ` Jerome Brunet
2020-07-27 14:13 ` Pierre-Louis Bossart
2020-07-27 15:15 ` Jerome Brunet
2020-07-27 15:26 ` Pierre-Louis Bossart
2020-07-29 15:46 ` [PATCH] ASoC: core: restore dpcm flags semantics Jerome Brunet
2020-07-29 15:56 ` Pierre-Louis Bossart
2020-07-30 9:04 ` Jerome Brunet
2020-07-30 16:06 ` Pierre-Louis Bossart
2020-07-30 18:52 ` Mark Brown
2020-07-31 12:16 ` Jerome Brunet
2020-07-31 17:42 ` Mark Brown [this message]
2020-07-31 8:06 ` Jerome Brunet
2020-07-30 18:12 ` Mark Brown
2020-07-31 18:54 ` [PATCH] ASoC: core: use less strict tests for dailink capabilities Mark Brown
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=20200731174207.GC4510@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=stephan@gerhold.net \
--cc=zhangn1985@outlook.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).