From: sashiko-bot@kernel.org
To: "Abel Vesa" <abel.vesa@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 2/5] arm64: dts: qcom: eliza-cqs-evk: Move sound card support to Eliza EVK generic
Date: Mon, 28 Sep 2026 16:41:04 +0000 [thread overview]
Message-ID: <20260928164105.030E31F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260928-dts-qcom-eliza-add-ufs-variant-v3-2-9a2fdbf6baf2@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] sound: hardcoded cqs model string in generic eliza-evk.dtsi
--
commit 59abb23a6bd8ac9951db58edd7aaebd3f7f631c7
Author: Abel Vesa <abel.vesa@oss.qualcomm.com>
arm64: dts: qcom: eliza-cqs-evk: Move sound card support to Eliza EVK generic
This patch moves the sound related device tree nodes from the Eliza CQS EVK
specific file to the generic Eliza EVK implementation. The stated goal is
to allow reuse across all variants, including the upcoming CQM EVK.
> diff --git a/arch/arm64/boot/dts/qcom/eliza-evk.dtsi b/arch/arm64/boot/dts/qcom/eliza-evk.dtsi
> index 6c5cc47a183ea..726fd8dd6c0d0 100644
> --- a/arch/arm64/boot/dts/qcom/eliza-evk.dtsi
> +++ b/arch/arm64/boot/dts/qcom/eliza-evk.dtsi
[ ... ]
> @@ -63,6 +65,55 @@ pmic_glink_ss_in: endpoint {
> };
> };
>
> + sound {
> + compatible = "qcom,eliza-sndcard", "qcom,sm8450-sndcard";
> + model = "eliza-cqs-evk";
[Severity: Low]
Since the eliza-evk.dtsi file is meant to be generically shared with other
variants like the Eliza CQM EVK, will hardcoding the model string to
"eliza-cqs-evk" in the shared sound node cause those other variants to
incorrectly advertise their ALSA sound card as the CQS EVK to userspace?
Could this model property be defined or overridden in the variant-specific
device tree files instead of the generic include?
> +
> + audio-routing = "SpkrLeft IN", "WSA_SPK1 OUT",
> + "SpkrRight IN", "WSA_SPK2 OUT",
> + "VA DMIC0", "vdd-micb",
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260928-dts-qcom-eliza-add-ufs-variant-v3-0-9a2fdbf6baf2@oss.qualcomm.com?part=2
next prev parent reply other threads:[~2026-09-28 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 16:36 [PATCH v3 0/5] arm64: dts: qcom: eliza-cqs-evk: Support eMMC and UFS SoMs Abel Vesa
2026-09-28 16:36 ` [PATCH v3 1/5] dt-bindings: arm: qcom: Describe Eliza CQS eMMC and UFS variants Abel Vesa
2026-09-28 16:36 ` [PATCH v3 2/5] arm64: dts: qcom: eliza-cqs-evk: Move sound card support to Eliza EVK generic Abel Vesa
2026-09-28 16:41 ` sashiko-bot [this message]
2026-09-28 16:36 ` [PATCH v3 3/5] arm64: dts: qcom: eliza: Separate common CQS SoM and eMMC configuration Abel Vesa
2026-09-28 16:36 ` [PATCH v3 4/5] arm64: dts: qcom: eliza: Add CQS SoM UFS variant Abel Vesa
2026-09-28 16:36 ` [PATCH v3 5/5] arm64: dts: qcom: eliza: Add CQS EVK " Abel Vesa
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=20260928164105.030E31F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox