From: sashiko-bot@kernel.org
To: "Chiluka Rohith" <rohith.chiluka@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v1] arm64: dts: qcom: glymur-crd: add DisplayPort audio DAI link
Date: Thu, 05 Nov 2026 10:56:52 +0000 [thread overview]
Message-ID: <sashiko-outbox-198891@kernel.org> (raw)
In-Reply-To: <20261105104624.621024-1-rohith.chiluka@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] arm64: dts: qcom: glymur-crd: dp-dai-link breaks sound probe on mahua-crd
--
commit a434cb6530336de83a46c26f22333629bcaaf510
Author: Chiluka Rohith <rohith.chiluka@oss.qualcomm.com>
arm64: dts: qcom: glymur-crd: add DisplayPort audio DAI link
This commit adds a DisplayPort RX DAI link to the sound node in
glymur-crd.dtsi, wiring the DISPLAY_PORT_RX_1 backend of q6apmbedai to the
mdss_dp1 controller.
> diff --git a/arch/arm64/boot/dts/qcom/glymur-crd.dtsi b/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
> index 58158b51fe295..eee75da201983 100644
> --- a/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
> +++ b/arch/arm64/boot/dts/qcom/glymur-crd.dtsi
> @@ -268,6 +268,22 @@ platform {
> };
> };
>
> + dp-dai-link {
> + link-name = "DISPLAY_PORT-RX";
> +
> + codec {
> + sound-dai = <&mdss_dp1>;
> + };
> +
> + cpu {
> + sound-dai = <&q6apmbedai DISPLAY_PORT_RX_1>;
> + };
> +
> + platform {
> + sound-dai = <&q6apm>;
> + };
> + };
[Severity: High]
Will adding this unconditionally enabled dp-dai-link node in glymur-crd.dtsi
break sound card probe on mahua-crd?
arch/arm64/boot/dts/qcom/glymur-crd.dtsi is shared by both glymur-crd.dts and
mahua-crd.dts:
arch/arm64/boot/dts/qcom/mahua-crd.dts:
#include "mahua.dtsi"
#include "glymur-crd.dtsi"
In arch/arm64/boot/dts/qcom/glymur.dtsi (included by both glymur-crd.dts and
mahua.dtsi), mdss_dp0 and mdss_dp1 default to disabled:
arch/arm64/boot/dts/qcom/glymur.dtsi:
mdss_dp1: displayport-controller@aea0000 {
...
#sound-dai-cells = <0>;
status = "disabled";
mdss_dp0 and mdss_dp1 are only enabled in glymur-crd.dts, while remaining
disabled in mahua.dtsi and mahua-crd.dts:
arch/arm64/boot/dts/qcom/glymur-crd.dts:
&mdss_dp0 {
status = "okay";
};
&mdss_dp1 {
status = "okay";
};
When x1e80100_platform_probe() -> qcom_snd_parse_of() parses the available
child nodes of /sound on mahua-crd, it calls:
qcom_snd_parse_of()
-> snd_soc_of_get_dai_link_codecs()
-> snd_soc_of_get_dlc()
-> snd_soc_get_dlc()
Because mdss_dp1 is disabled on mahua-crd, the DP controller never probes or
registers its hdmi-audio-codec ASoC component, causing snd_soc_get_dlc() to
return -EPROBE_DEFER indefinitely and preventing the entire sound card (and
existing WSA speaker and VA capture links) from probing on Mahua CRD.
In addition, glymur-crd.dts enables both mdss_dp0 and mdss_dp1, whereas this
patch only adds a DAI link for mdss_dp1. Should the DP DAI link(s) match the
enabled DP controllers and only be enabled where the corresponding mdss_dp
nodes are enabled?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261105104624.621024-1-rohith.chiluka@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-11-05 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 10:46 [PATCH v1] arm64: dts: qcom: glymur-crd: add DisplayPort audio DAI link Chiluka Rohith
2026-11-05 10:56 ` sashiko-bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-05 10:46 Chiluka Rohith
2026-11-05 11:11 ` sashiko-bot
2026-11-05 12:07 ` Konrad Dybcio
2026-11-05 10:40 Chiluka Rohith
2026-11-05 11:03 ` sashiko-bot
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=sashiko-outbox-198891@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rohith.chiluka@oss.qualcomm.com \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.