From: sashiko-bot@kernel.org
To: "Sibi Sankar" <sibi.sankar@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH V8 2/2] arm64: dts: qcom: glymur-crd: add Audio sound card node
Date: Wed, 20 May 2026 15:06:55 +0000 [thread overview]
Message-ID: <20260520150655.DCAB41F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260520141828.2724689-3-sibi.sankar@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] The `audio-routing` property uses lowercase strings, which will fail to match the dynamically created ALSA ASoC DAPM widgets, leaving the speakers disconnected.
- [High] The right woofer is incorrectly routed to the SPK2 output instead of SPK1, which breaks the audio stream routing.
--
commit 4086f61ae4a41fcc2e29b8dbcc7878956275252b
Author: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
arm64: dts: qcom: glymur-crd: add Audio sound card node
This commit adds the sound card node for the Glymur-crd board. It defines
the audio routing for speakers and adds device nodes for the WSA884x
smart speakers and DMIC microphones.
> diff --git a/arch/arm64/boot/dts/qcom/glymur-crd.dtsi b/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
> index e784b538f42e1..4c00d09f766c2 100644
> --- a/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
> +++ b/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
> @@ -68,6 +68,54 @@ switch-lid {
> };
> };
>
> + sound {
> + compatible = "qcom,glymur-sndcard";
> + model = "GLYMUR-CRD";
> + audio-routing = "wooferleft in", "wsa wsa_spk1 out",
> + "tweeterleft in", "wsa wsa_spk2 out",
> + "wooferright in", "wsa2 wsa_spk2 out",
[Severity: High]
ALSA DAPM string matching for audio routing is exact and case-sensitive.
The widgets are created with names derived from sound-name-prefix (e.g.,
WooferLeft) and the widget type suffix (e.g., IN), making the expected name
"WooferLeft IN".
Similarly, the WSA macros create widgets with uppercase names like
"WSA WSA_SPK1 OUT".
Does using lowercase names here cause snd_soc_dapm_add_route() to silently
fail to find the matching widgets, leaving the speakers disconnected?
[Severity: High]
The right_woofer node defines qcom,port-mapping = <1 2 3 7 12 14>, which
corresponds to the first SoundWire stream on the WSA2 macro. This first
stream connects to the WSA2 WSA_SPK1 OUT DAPM widget.
Could routing wooferright to wsa2 wsa_spk2 out connect the woofer to the
tweeter's stream instead, breaking the crossover and preventing the right
woofer from receiving its proper audio stream?
[ ... ]
> +&swr3 {
> + status = "okay";
> +
> + /* WSA8845, Right Woofer */
> + right_woofer: speaker@0,0 {
> + compatible = "sdw20217020400";
> + reg = <0 0>;
> + reset-gpios = <&lpass_tlmm 13 GPIO_ACTIVE_LOW>;
> + #sound-dai-cells = <0>;
> + sound-name-prefix = "WooferRight";
> + vdd-1p8-supply = <&vreg_l15b_e0_1p8>;
> + vdd-io-supply = <&vreg_l18b_e0_1p2>;
> + qcom,port-mapping = <1 2 3 7 12 14>;
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260520141828.2724689-1-sibi.sankar@oss.qualcomm.com?part=2
prev parent reply other threads:[~2026-05-20 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 14:18 [PATCH V8 0/2] Enable ADSP and CDSP for Glymur SoC Sibi Sankar
2026-05-20 14:18 ` [PATCH V8 1/2] arm64: dts: glymur: Add LPASS macro codecs and pinctrl Sibi Sankar
2026-05-20 14:44 ` sashiko-bot
2026-05-20 14:18 ` [PATCH V8 2/2] arm64: dts: qcom: glymur-crd: add Audio sound card node Sibi Sankar
2026-05-20 15:06 ` sashiko-bot [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=20260520150655.DCAB41F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sibi.sankar@oss.qualcomm.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