All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Val Packett" <val@packett.cool>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 5/5] arm64: dts: qcom: motorola-dubai: Add sound card with aw88261 speakers
Date: Fri, 16 Oct 2026 08:00:32 +0000	[thread overview]
Message-ID: <sashiko-outbox-173985@kernel.org> (raw)
In-Reply-To: <20261016073157.611956-6-val@packett.cool>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] dt-bindings: aw88261 audio channel assignment inverted
- [Low] commit-message: inaccurate description of power-domains removal
--

commit df15644ca6ae81e8d6c78e4e8358dd5c5c68d8f0
Author: Val Packett <val@packett.cool>
arm64: dts: qcom: motorola-dubai: Add sound card with aw88261 speakers

This commit enables the sndcard node with MultiMedia frontends, a USB offload
RX link, and two aw88261 speaker amplifiers. It also fixes the audiocc
compatible string and removes power-domains from a node.

> While here, use the correct compatible for audiocc for this phone,
> and remove references to power-domains from a 'reserved' node.

[Severity: Low]
Is this description accurate? The patch code removes the power-domains
property from lpass_audiocc, which is a clock controller, not a reserved
memory node.

> diff --git a/arch/arm64/boot/dts/qcom/sm7325-motorola-dubai-common.dtsi b/arch/arm64/boot/dts/qcom/sm7325-motorola-dubai-common.dtsi
> index 3860ab8508a09..1e1c195de1af1 100644
> --- a/arch/arm64/boot/dts/qcom/sm7325-motorola-dubai-common.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm7325-motorola-dubai-common.dtsi

[ ... ]

> @@ -699,6 +701,40 @@ &gpu_zap_shader {
>  	firmware-name = "qcom/sm7325/motorola/dubai/a660_zap.mbn";
>  };
>  
> +&i2c1 {
> +	clock-frequency = <100000>;
> +
> +	status = "okay";
> +
> +	/* Bottom speaker */
> +	aw88261_r: audio-codec@34 {
> +		compatible = "awinic,aw88261";
> +		reg = <0x34>;
> +
> +		dvdd-supply = <&vreg_l18b_1p8>;
> +		sound-name-prefix = "Amplifier R";
> +		firmware-name = "qcom/sm7325/motorola/dubai/aw88261_acf.bin";
> +
> +		awinic,audio-channel = <0>;

[Severity: Medium]
Does this assign the right physical speaker to the left audio channel?
Channel 0 is typically the left channel, which contradicts the
"Amplifier R" and "Bottom speaker" designation. This might result
in inverted stereo audio playback.

> +
> +		#sound-dai-cells = <0>;
> +	};
> +
> +	/* Top speaker / ear speaker */
> +	aw88261_l: audio-codec@35 {
> +		compatible = "awinic,aw88261";
> +		reg = <0x35>;
> +
> +		dvdd-supply = <&vreg_l18b_1p8>;
> +		sound-name-prefix = "Amplifier L";
> +		firmware-name = "qcom/sm7325/motorola/dubai/aw88261_acf.bin";
> +
> +		awinic,audio-channel = <1>;

[Severity: Medium]
Similarly, does this assign the left physical speaker to the right audio
channel? Assigning 1 (typically the right channel) to the top/left
speaker contradicts its physical placement and name.

> +
> +		#sound-dai-cells = <0>;
> +	};
> +};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261016073157.611956-1-val@packett.cool?part=5

  reply	other threads:[~2026-10-16  8:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16  7:31 [PATCH 0/5] Enable soundcard on Motorola Edge 30 Val Packett
2026-10-16  7:31 ` [PATCH 1/5] ASoC: qcom: qdsp6: q6routing: add Senary MI2S ports Val Packett
2026-10-16  7:31 ` [PATCH 2/5] ASoC: qcom: sm8250: add Senary MI2S RX support Val Packett
2026-10-16  7:47   ` sashiko-bot
2026-10-16  7:31 ` [PATCH 3/5] ASoC: dt-bindings: qcom,sm8250: Add Motorola Edge 30 sound card Val Packett
2026-10-16  7:31 ` [PATCH 4/5] ASoC: qcom: sm8250: Add motorola-dubai soundcard compatible Val Packett
2026-10-16  7:31 ` [PATCH 5/5] arm64: dts: qcom: motorola-dubai: Add sound card with aw88261 speakers Val Packett
2026-10-16  8:00   ` sashiko-bot [this message]
2026-10-16  8:04     ` Val Packett

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-173985@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=val@packett.cool \
    /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.