From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Mark Brown <broonie@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
bard.liao@intel.com
Cc: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 0/4] ASoC: makes CPU/Codec channel connection map more generic
Date: Tue, 10 Oct 2023 09:43:16 -0400 [thread overview]
Message-ID: <4ee736cc-25cd-4e33-95b3-fb1607e9a998@linux.intel.com> (raw)
In-Reply-To: <87bkd78e88.wl-kuninori.morimoto.gx@renesas.com>
On 10/9/23 21:20, Kuninori Morimoto wrote:
>
> Hi Mark
> Cc Bard, Pierre-Louis
>
> Current ASoC is supporting CPU/Codec = N:M (N < M) connection by using
> ch_map idea. This patch expand that all connection uses this idea,
> and no limit of N < M [1].
>
> This patch is tested on Audio-Graph-Card2 with sample dtsi,
> but needs Tested-by, at least from Intel.
We can test the next version (comments in separate mail) but we don't
have a configuration with more cpu dais than codec dais I am afraid, so
the best we can contribute is a non-regression for the N < M case.
prev parent reply other threads:[~2023-10-10 13:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 1:20 [PATCH 0/4] ASoC: makes CPU/Codec channel connection map more generic Kuninori Morimoto
2023-10-10 1:21 ` [PATCH 1/4] " Kuninori Morimoto
2023-10-10 13:40 ` Pierre-Louis Bossart
2023-10-10 23:26 ` Kuninori Morimoto
2023-10-10 1:21 ` [PATCH 2/4] ASoC: audio-graph-card2: add CPU:Codec = N:M support Kuninori Morimoto
2023-10-10 1:21 ` [PATCH 3/4] ASoC: audio-graph-card2-custom-sample: add CPU/Codec = N:M sample Kuninori Morimoto
2023-10-10 1:21 ` [PATCH 4/4] dt-bindings: audio-graph-port: ch_maps property Kuninori Morimoto
2023-10-11 14:20 ` Krzysztof Kozlowski
2023-10-10 13:43 ` Pierre-Louis Bossart [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=4ee736cc-25cd-4e33-95b3-fb1607e9a998@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--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