From: sashiko-bot@kernel.org
To: "David Heidelberg" <david@ixit.cz>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 6/8] arm64: dts: qcom: sdm845-google: Add basic audio support
Date: Thu, 24 Sep 2026 13:37:21 +0000 [thread overview]
Message-ID: <20260924133721.ADEFF1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260924-pixel3-audio-v4-6-85b5d133aa5e@ixit.cz>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dts: incorrect sound card model name propagated to crosshatch
--
commit cc7bf455060c791244c0b8599e2eec24bc61fc65
Author: David Heidelberg <david@ixit.cz>
arm64: dts: qcom: sdm845-google: Add basic audio support
Introduce support for sound card and wire two CS35L36 audio codecs for
top and bottom speakers.
> diff --git a/arch/arm64/boot/dts/qcom/sdm845-google-common.dtsi b/arch/arm64/boot/dts/qcom/sdm845-google-common.dtsi
> index f1379857e2742..bc826d211e4a7 100644
> --- a/arch/arm64/boot/dts/qcom/sdm845-google-common.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sdm845-google-common.dtsi
[ ... ]
> @@ -474,6 +537,39 @@ &qup_uart9_tx {
> bias-disable;
> };
>
> +&sound {
> + compatible = "qcom,sdm845-sndcard";
> + model = "blueline";
[Severity: Low]
Because sdm845-google-common.dtsi is shared and included by the Pixel 3 XL
board file (sdm845-google-crosshatch.dts), does this hardcoded ALSA sound
card model incorrectly propagate to crosshatch devices?
Since crosshatch does not override the &sound node's model property, its sound
card will identify itself as 'blueline' to userspace ALSA subsystems (e.g.,
UCM profiles).
Should this use a generic name here and get overridden in the leaf dts instead?
> + pinctrl-0 = <&quat_mi2s_active>, <&quat_mi2s_sd0_active>,
> + <&quat_mi2s_sd1_active>;
> + pinctrl-names = "default";
> +
> + /* mm[0-9]-dai-link nodes must be positioned first regardless of sorting */
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260924-pixel3-audio-v4-0-85b5d133aa5e@ixit.cz?part=6
next prev parent reply other threads:[~2026-09-24 13:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 13:24 [PATCH v4 0/8] Speakers for Pixel 3 / 3 XL David Heidelberg via B4 Relay
2026-09-24 13:24 ` David Heidelberg
2026-09-24 13:24 ` [PATCH v4 1/8] ASoC: qcom: sdm845: Demystify TDM masks a bit David Heidelberg via B4 Relay
2026-09-24 13:24 ` David Heidelberg
2026-09-24 13:34 ` sashiko-bot
2026-09-25 8:14 ` Srinivas Kandagatla
2026-09-24 13:24 ` [PATCH v4 2/8] ASoC: qcom: sdm845: use DSP_A format for TDM codec DAIs David Heidelberg via B4 Relay
2026-09-24 13:24 ` David Heidelberg
2026-09-25 8:22 ` Srinivas Kandagatla
2026-09-24 13:24 ` [PATCH v4 3/8] ASoC: qcom: sdm845: Use per-speaker RX masks for TDM slot assignment David Heidelberg via B4 Relay
2026-09-24 13:24 ` David Heidelberg
2026-09-25 8:23 ` Srinivas Kandagatla
2026-09-24 13:24 ` [PATCH v4 4/8] ASoC: qcom: sdm845: Set codec dai and component sysclk during startup David Heidelberg via B4 Relay
2026-09-24 13:24 ` David Heidelberg
2026-09-25 8:26 ` Srinivas Kandagatla
2026-09-24 13:24 ` [PATCH v4 5/8] ASoC: cs35l36: Implement set_tdm_slot to program RX and TX slots David Heidelberg via B4 Relay
2026-09-24 13:24 ` David Heidelberg
2026-09-24 13:36 ` sashiko-bot
2026-09-24 13:24 ` [PATCH v4 6/8] arm64: dts: qcom: sdm845-google: Add basic audio support David Heidelberg via B4 Relay
2026-09-24 13:24 ` David Heidelberg
2026-09-24 13:37 ` sashiko-bot [this message]
2026-09-24 13:24 ` [PATCH v4 7/8] slimbus: qcom-ngd-ctrl: Remove data channels on stream disable David Heidelberg via B4 Relay
2026-09-24 13:24 ` David Heidelberg
2026-09-24 13:36 ` sashiko-bot
2026-09-25 8:09 ` Srinivas Kandagatla
2026-09-25 8:34 ` David Heidelberg
2026-09-25 14:30 ` David Heidelberg
2026-09-24 13:24 ` [PATCH v4 8/8] arm64: dts: qcom: sdm845-google: Add WCD9340 codec and microphone capture David Heidelberg via B4 Relay
2026-09-24 13:24 ` David Heidelberg
2026-09-24 14:11 ` [PATCH v4 0/8] Speakers for Pixel 3 / 3 XL Mark Brown
2026-09-24 14:13 ` David Heidelberg
2026-09-25 11:18 ` (subset) " Mark Brown
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=20260924133721.ADEFF1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--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 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.