From: Ravi Hothi <ravi.hothi@oss.qualcomm.com>
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,
mohammad.rafi.shaik@oss.qualcomm.com,
ajay.nandam@oss.qualcomm.com
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: eliza-cqs-evk: Enable sound card support with WSA8845 and DMIC
Date: Wed, 22 Jul 2026 13:00:59 +0530 [thread overview]
Message-ID: <24cac124-7d04-400d-83df-bdcecdddb7de@oss.qualcomm.com> (raw)
In-Reply-To: <8dba00d9-65c5-4891-95c1-67f55664aa79@oss.qualcomm.com>
On 7/17/2026 1:59 PM, Konrad Dybcio wrote:
> On 7/13/26 2:18 PM, Ravi Hothi wrote:
>> Enable the sound card on the Eliza CQS EVK platform, including the
>> WSA8845 external speaker path and DMIC microphone capture via VA macro.
>>
>> Enable the required LPASS WSA macro, VA macro and SoundWire controller
>> along with the necessary pinctrl configurations for DMIC and WSA
>> SoundWire interfaces.
>>
>> Signed-off-by: Ravi Hothi <ravi.hothi@oss.qualcomm.com>
>> ---
>
> [...]
>
>> + sound {
>> + compatible = "qcom,eliza-sndcard", "qcom,sm8450-sndcard";
>> + model = "eliza-cqs-evk";
>
> Is there a reason only the CQS EVK gets audio support?
> i.e. is this setup not common across all the EVKs?
Currently we only have the CQS EVK upstream. Future EVK variants may
have a different audio codec or configuration, so we are adding audio
support specific to the CQS EVK for now.
Thanks,
Ravi Hothi
>> +
>> + audio-routing = "SpkrLeft IN", "WSA_SPK1 OUT",
>> + "SpkrRight IN", "WSA_SPK2 OUT",
>> + "VA DMIC0", "vdd-micb",
>> + "VA DMIC1", "vdd-micb",
>> + "VA DMIC2", "vdd-micb",
>> + "VA DMIC3", "vdd-micb",
>> + "VA DMIC4", "vdd-micb",
>> + "VA DMIC5", "vdd-micb",
>> + "VA DMIC6", "vdd-micb",
>> + "VA DMIC7", "vdd-micb";
>
> Are there actually 8 DMICs?
Yes, there are 8 DMICs
Thanks,
Ravi Hothi
>
>> +
>> + va-dai-link {
>> + link-name = "VA Capture";
>> +
>> + cpu {
>> + sound-dai = <&q6apmbedai VA_CODEC_DMA_TX_0>;
>> + };
>> +
>> + codec {
>
> 'co'dec < 'cp'u
ACK, Will update in next version.
Thanks,
Ravi Hothi
>
> [...]
>
>> + dmic_eldo: regulator-dmic-eldo {
>> + compatible = "regulator-fixed";
>> + regulator-name = "dmic-eldo";
>> + regulator-min-microvolt = <1800000>;
>> + regulator-max-microvolt = <1800000>;
>> + gpio = <&pm7550_gpios 8 GPIO_ACTIVE_HIGH>;
>> + enable-active-high;
>> + vin-supply = <&vreg_bob>;
>> + regulator-boot-on;
>
> Is it really boot-on?
Good catch, regulator-boot-on is not needed here.
Will fix in the next version.
Thanks,
Ravi Hothi
>
>> + };
>> +};
>> +
>> +&tlmm {
>
> Label references should be sorted alphabetically
ACK, Will update in next version.
Thanks,
Ravi Hothi
>
>> + spkr_1_sd_n_active: spkr-1-sd-n-active-state {
>> + pins = "gpio59";
>> + function = "gpio";
>> + drive-strength = <16>;
>> + bias-disable;
>> + output-low;
>
> TLMM pins should not assert output state in the pinconf, the driver will
> take care of that through the GPIOD APIs
ACK, Will update in next version.
Thanks,
Ravi Hothi
>
> On a note, these normally go through LPASS_TLMM, but I'm going to guess
> these pins are not muxable to ADSP?
>
No, these GPIOs are not muxable to ADSP/LPASS on eliza. The WSA8845 SD_N
lines are connected to main TLMM GPIOs on this board, not LPASS TLMM.
Thanks,
Ravi Hothi
> Konrad
prev parent reply other threads:[~2026-07-22 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 12:18 [PATCH v2 0/2] arm64: dts: qcom: eliza: Add audio support Ravi Hothi
2026-07-13 12:18 ` [PATCH v2 1/2] arm64: dts: qcom: eliza: Add LPASS macro and SoundWire support Ravi Hothi
2026-07-17 8:25 ` Konrad Dybcio
2026-07-22 7:16 ` Ravi Hothi
2026-07-13 12:18 ` [PATCH v2 2/2] arm64: dts: qcom: eliza-cqs-evk: Enable sound card support with WSA8845 and DMIC Ravi Hothi
2026-07-17 8:29 ` Konrad Dybcio
2026-07-22 7:30 ` Ravi Hothi [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=24cac124-7d04-400d-83df-bdcecdddb7de@oss.qualcomm.com \
--to=ravi.hothi@oss.qualcomm.com \
--cc=ajay.nandam@oss.qualcomm.com \
--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=mohammad.rafi.shaik@oss.qualcomm.com \
--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
all inboxes | Powered by JetHome®