[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fcf845bd-9803-ab04-d2a9-c258ddfcc972@linaro.org>
Date: Wed, 18 Mar 2020 15:57:38 +0000
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
broonie@...nel.org
Cc: alsa-devel@...a-project.org, lgirdwood@...il.com, perex@...ex.cz,
linux-kernel@...r.kernel.org, vkoul@...nel.org
Subject: Re: [PATCH 1/2] ASoC: qcom: sdm845: handle soundwire stream
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>;
};
};
--srini
Powered by blists - more mailing lists