From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sm8750-mtp: Add sound (speakers, headset codec, dmics)
Date: Mon, 28 Apr 2025 16:41:53 +0200 [thread overview]
Message-ID: <e61e17ca-fed7-4712-96fc-a9a2339de1fb@linaro.org> (raw)
In-Reply-To: <dd271e8c-e430-4e6d-88ca-95eabe61ce94@oss.qualcomm.com>
On 25/04/2025 11:30, Konrad Dybcio wrote:
> On 4/24/25 11:40 AM, Krzysztof Kozlowski wrote:
>> Add device nodes for most of the sound support - WSA883x smart speakers,
>> WCD9395 audio codec (headset) and sound card - which allows sound
>> playback via speakers and recording via DMIC microphones. Changes bring
>> necessary foundation for headset playback/recording via USB, but that
>> part is not yet ready.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
>
> [...]
>
>> + sound {
>> + compatible = "qcom,sm8750-sndcard", "qcom,sm8450-sndcard";
>> + model = "SM8750-MTP";
>> + audio-routing = "SpkrLeft IN", "WSA_SPK1 OUT",
>> + "SpkrRight IN", "WSA_SPK2 OUT",
>> + "IN1_HPHL", "HPHL_OUT",
>> + "IN2_HPHR", "HPHR_OUT",
>> + "AMIC2", "MIC BIAS2",
>> + "VA DMIC0", "MIC BIAS3", /* MIC4 on schematics */
>> + "VA DMIC1", "MIC BIAS3", /* MIC1 on schematics */
>
> Is this a mistake in what the codec driver exposes, or just a fumble
> in numbering $somewhere?
Which mistake? MIC4? Schematics call name things differently. They
always were, so to make it clear for people without schematics I wrote
which MIC it actually is.
>
>> + "VA DMIC2", "MIC BIAS1",
>> + "VA DMIC3", "MIC BIAS1",
>> + "VA DMIC0", "VA MIC BIAS3",
>> + "VA DMIC1", "VA MIC BIAS3",
>> + "VA DMIC2", "VA MIC BIAS1",
>> + "VA DMIC3", "VA MIC BIAS1",
>> + "TX SWR_INPUT1", "ADC2_OUTPUT";
>> +
>> + wcd-playback-dai-link {
>> + link-name = "WCD Playback";
>> +
>> + cpu {
>> + sound-dai = <&q6apmbedai RX_CODEC_DMA_RX_0>;
>> + };
>> +
>> + codec {
>
> 'co'dec < 'cp'u
>
> [...]
That was the convention so far, but we can start a new one, sure. Just
ask the same all other patch contributors, because each of them will be
copying old code, which means cpu->codec->platform
>
>> + /*
>> + * WCD9395 RX Port 1 (HPH_L/R) <=> SWR1 Port 1 (HPH_L/R)
>> + * WCD9395 RX Port 2 (CLSH) <=> SWR1 Port 2 (CLSH)
>> + * WCD9395 RX Port 3 (COMP_L/R) <=> SWR1 Port 3 (COMP_L/R)
>> + * WCD9395 RX Port 4 (LO) <=> SWR1 Port 4 (LO)
>> + * WCD9395 RX Port 5 (DSD_L/R) <=> SWR1 Port 5 (DSD_L/R)
>> + * WCD9395 RX Port 6 (HIFI_PCM_L/R) <=> SWR1 Port 9 (HIFI_PCM_L/R)
>> + */
>> + qcom,rx-port-mapping = <1 2 3 4 5 9>;
>
> Does this deserve some dt-bindings constants?
No, because these are hardware details/constants. Drivers do not use them.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-28 14:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 9:40 [PATCH 0/2] arm64: dts: qcom: sm8750: Add sound Krzysztof Kozlowski
2025-04-24 9:40 ` [PATCH 1/2] arm64: dts: qcom: sm8750: Add Soundwire nodes Krzysztof Kozlowski
2025-04-25 9:24 ` Konrad Dybcio
2025-05-08 10:37 ` Krzysztof Kozlowski
2025-05-12 19:38 ` Konrad Dybcio
2025-05-13 8:26 ` Krzysztof Kozlowski
2025-05-16 11:36 ` Konrad Dybcio
2025-05-16 21:46 ` Dmitry Baryshkov
2025-04-24 9:40 ` [PATCH 2/2] arm64: dts: qcom: sm8750-mtp: Add sound (speakers, headset codec, dmics) Krzysztof Kozlowski
2025-04-25 9:30 ` Konrad Dybcio
2025-04-28 14:41 ` Krzysztof Kozlowski [this message]
2025-04-29 19:11 ` Konrad Dybcio
2025-04-30 6:19 ` Krzysztof Kozlowski
2025-04-30 10:48 ` Konrad Dybcio
2025-04-30 11:07 ` neil.armstrong
2025-04-30 11:17 ` Konrad Dybcio
2025-04-30 11:18 ` Krzysztof Kozlowski
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=e61e17ca-fed7-4712-96fc-a9a2339de1fb@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).