From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, broonie@kernel.org
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com, perex@perex.cz,
linux-kernel@vger.kernel.org, vkoul@kernel.org
Subject: Re: [PATCH 1/2] ASoC: qcom: sdm845: handle soundwire stream
Date: Wed, 18 Mar 2020 11:53:59 -0500 [thread overview]
Message-ID: <c8738ecf-727f-2063-8aa0-46fc1c338383@linux.intel.com> (raw)
In-Reply-To: <fcf845bd-9803-ab04-d2a9-c258ddfcc972@linaro.org>
On 3/18/20 10:57 AM, Srinivas Kandagatla wrote:
>
>
> On 18/03/2020 15:26, Pierre-Louis Bossart wrote:
>>
>> Same comment, how does the notion of cpu_dai come in the picture for a
>> SoundWire dailink?
>> Would you mind listing what the components of the dailinks are?
>
> dais that I was referring here are all codec dais from backend-dai.
>
> Device tree entries from
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm64/boot/dts/qcom/sdm845-db845c.dts?h=next-20200318#n538
>
>
>
> Frontend-dai:
> mm1-dai-link {
> link-name = "MultiMedia1";
> cpu {
> sound-dai = <&q6asmdai MSM_FRONTEND_DAI_MULTIMEDIA1>;
> };
> };
>
> Backend-dai:
> slim-dai-link {
> link-name = "SLIM Playback";
> cpu {
> sound-dai = <&q6afedai SLIMBUS_0_RX>;
> };
>
> platform {
> sound-dai = <&q6routing>;
> };
>
> codec {
> sound-dai = <&left_spkr>, <&right_spkr>, <&swm 0>,
> <&wcd9340 0>;
> };
Thanks, I didn't realize this and now understand your point.
I guess that means we've officially stretched the limits of the DPCM
model though, lumping all codec dais from separate devices into the same
'backend' doesn't seem like a very good path forward, we'd really need a
notion of domain to represent such bridges.
For now for the series
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
next prev parent reply other threads:[~2020-03-18 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 9:53 [PATCH 0/2] ASoC: sdm845: fix soundwire stream handling Srinivas Kandagatla
2020-03-17 9:53 ` [PATCH 1/2] ASoC: qcom: sdm845: handle soundwire stream Srinivas Kandagatla
2020-03-17 13:07 ` Pierre-Louis Bossart
2020-03-18 11:59 ` Srinivas Kandagatla
2020-03-18 15:26 ` Pierre-Louis Bossart
2020-03-18 15:57 ` Srinivas Kandagatla
2020-03-18 16:53 ` Pierre-Louis Bossart [this message]
2020-03-17 9:53 ` [PATCH 2/2] ASoC: codecs: wsa881x: remove soundwire stream handling Srinivas Kandagatla
2020-03-17 11:05 ` [PATCH 0/2] ASoC: sdm845: fix " Pierre-Louis Bossart
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=c8738ecf-727f-2063-8aa0-46fc1c338383@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=srinivas.kandagatla@linaro.org \
--cc=vkoul@kernel.org \
/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).