From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [PATCH 0/7] ASoC: Merge CPU/Codec DAIs
Date: Wed, 11 Mar 2020 17:10:33 +0000 [thread overview]
Message-ID: <20200311171033.GI5411@sirena.org.uk> (raw)
In-Reply-To: <8e92f00a-6fb4-84e6-8e48-28b9913791c0@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
On Wed, Mar 11, 2020 at 09:36:17AM -0500, Pierre-Louis Bossart wrote:
> I would still like to make sure we have an broadbrush idea of what the 2nd
> step might be. It seems to me it's not possible to avoid having a notion of
> source/sink inside of a dailink (the wording is probably not right e.g. for
> full duplex, maybe domain1/domain2 component1/component2 are more accurate).
> The dais are exposed by different components and are really the hook by
> which the components can be configured with compatible settings.
We at least have the notion of clock master but that's something that
could potentially vary at runtime so not stable. Like you say finding
appropriate language to talk about these things is tricky and I'm also
struggling to think of anything better than numbered components.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-03-11 17:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 1:06 [PATCH 0/7] ASoC: Merge CPU/Codec DAIs Kuninori Morimoto
2020-03-11 1:07 ` [PATCH 1/7] ASoC: soc-core: " Kuninori Morimoto
2020-03-11 1:07 ` [PATCH 2/7] ASoC: soc-core: Merge for_each_rtd_cpu/codec_dais() Kuninori Morimoto
2020-03-11 1:07 ` [PATCH 3/7] ASoC: soc-dapm: " Kuninori Morimoto
2020-03-11 1:27 ` Sridharan, Ranjani
2020-03-11 1:30 ` Kuninori Morimoto
2020-03-11 1:07 ` [PATCH 4/7] ASoC: soc-pcm: " Kuninori Morimoto
2020-03-11 1:30 ` Sridharan, Ranjani
2020-03-11 2:06 ` Kuninori Morimoto
2020-03-11 1:07 ` [PATCH 5/7] ASoC: soc-core: Merge CPU/Codec for soc_dai_pcm_new() Kuninori Morimoto
2020-03-11 1:07 ` [PATCH 6/7] ASoC: soc-pcm: Merge CPU/Codec MSB at soc_pcm_apply_msb() Kuninori Morimoto
2020-03-11 1:07 ` [PATCH 7/7] ASoC: soc-pcm: Merge CPU/Codec at soc_pcm_pointer() Kuninori Morimoto
2020-03-11 2:00 ` Pierre-Louis Bossart
2020-03-11 2:39 ` Kuninori Morimoto
2020-03-11 1:51 ` [PATCH 0/7] ASoC: Merge CPU/Codec DAIs Pierre-Louis Bossart
2020-03-11 2:27 ` Kuninori Morimoto
2020-03-11 14:36 ` Pierre-Louis Bossart
2020-03-11 17:10 ` Mark Brown [this message]
2020-03-12 1:17 ` Kuninori Morimoto
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=20200311171033.GI5411@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=pierre-louis.bossart@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.