From: Mark Brown <broonie@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>,
alsa-devel@alsa-project.org, tiwai@suse.de,
Daniel Baluta <daniel.baluta@gmail.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>
Subject: Re: [PATCH 1/4] ASoC: soc-pcm: dpcm: fix playback/capture checks
Date: Thu, 18 Jun 2020 16:01:43 +0100 [thread overview]
Message-ID: <20200618150143.GJ5789@sirena.org.uk> (raw)
In-Reply-To: <20200617174635.GA40060@gerhold.net>
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
On Wed, Jun 17, 2020 at 07:46:35PM +0200, Stephan Gerhold wrote:
> At the end the question is if those machine drivers that have
> dpcm_playback/capture hardcoded just set it because it was required to
> make DPCM work, or if they actually use it to restrict the direction of
> a DAI link.
The other question would be if they are restricting it to limit the
direction of a DAI link beyond the limits that the hardware has why are
they doing that? I'm not sure that'd be a sensible thing to do.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-18 15:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 19:44 [PATCH 0/4] ASoC: Fix dailink checks for DPCM Pierre-Louis Bossart
2020-06-08 19:44 ` [PATCH 1/4] ASoC: soc-pcm: dpcm: fix playback/capture checks Pierre-Louis Bossart
2020-06-16 8:54 ` Stephan Gerhold
2020-06-16 9:02 ` Stephan Gerhold
2020-06-16 14:23 ` Pierre-Louis Bossart
2020-06-16 14:52 ` Mark Brown
2020-06-16 15:05 ` Pierre-Louis Bossart
2020-06-16 15:55 ` Stephan Gerhold
2020-06-16 16:32 ` Pierre-Louis Bossart
2020-06-16 17:05 ` Pierre-Louis Bossart
2020-06-17 9:01 ` Stephan Gerhold
2020-06-17 14:33 ` Pierre-Louis Bossart
2020-06-17 17:46 ` Stephan Gerhold
2020-06-18 15:01 ` Mark Brown [this message]
2020-06-18 15:45 ` Pierre-Louis Bossart
2020-06-22 17:54 ` Stephan Gerhold
2020-06-22 17:59 ` Mark Brown
2020-06-16 16:42 ` Mark Brown
2020-07-17 13:42 ` Jerome Brunet
2020-07-17 17:13 ` Pierre-Louis Bossart
2020-07-17 18:18 ` Mark Brown
2020-07-17 18:34 ` Pierre-Louis Bossart
2020-06-08 19:44 ` [PATCH 2/4] ASoC: core: only convert non DPCM link to DPCM link Pierre-Louis Bossart
2020-06-08 19:44 ` [PATCH 3/4] ASoC: Intel: boards: replace capture_only by dpcm_capture Pierre-Louis Bossart
2020-06-08 19:44 ` [PATCH 4/4] ASoC: SOF: nocodec: conditionally set dpcm_capture/dpcm_playback flags Pierre-Louis Bossart
2020-06-09 15:28 ` [PATCH 0/4] ASoC: Fix dailink checks for DPCM 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=20200618150143.GJ5789@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.baluta@gmail.com \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=stephan@gerhold.net \
--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 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.