From: sashiko-bot@kernel.org
To: "Hongyang Zhao" <hongyang.zhao@thundersoft.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 4/5] ASoC: qcom: sc8280xp: Add per-card data
Date: Sat, 06 Jun 2026 21:28:06 +0000 [thread overview]
Message-ID: <20260606212806.ECF611F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260607-rubikpi-next-20260605-v1-4-7f334e16fea6@thundersoft.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incorrect DAPM pin mask for 'Mic Jack' in qcs6490_rubikpi3_headset_jack_pins causes microphone detection failure.
--
commit 869054356ad0f6ae035a50e1d5d5e99577638b9b
Author: Hongyang Zhao <hongyang.zhao@thundersoft.com>
ASoC: qcom: sc8280xp: Add per-card data
This commit converts the sc8280xp machine driver match data to a per-card data
structure to support board-specific MI2S codec requirements. It adds data for
the QCS6490 RubikPi3 and a common headset jack helper.
> diff --git a/sound/soc/qcom/sc8280xp.c b/sound/soc/qcom/sc8280xp.c
> index 7925aa3f63ba0..1ccd7437cc52d 100644
> --- a/sound/soc/qcom/sc8280xp.c
> +++ b/sound/soc/qcom/sc8280xp.c
[ ... ]
> +static struct snd_soc_jack_pin qcs6490_rubikpi3_headset_jack_pins[] = {
> + {
> + .pin = "Mic Jack",
> + .mask = SND_JACK_HEADPHONE,
[Severity: Medium]
Does this mask prevent correct DAPM routing for the microphone? It looks like
SND_JACK_HEADPHONE is used instead of SND_JACK_MICROPHONE for the Mic Jack pin.
> + },
> + {
> + .pin = "Headphone Jack",
> + .mask = SND_JACK_HEADPHONE,
> + },
> +};
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260607-rubikpi-next-20260605-v1-0-7f334e16fea6@thundersoft.com?part=4
next prev parent reply other threads:[~2026-06-06 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 18:58 [PATCH 0/5] Add audio support for QCS6490 RubikPi3 Hongyang Zhao
2026-06-06 18:58 ` [PATCH 1/5] ASoC: dt-bindings: es8316: Document jack detect inversion Hongyang Zhao
2026-06-06 18:58 ` [PATCH 2/5] ASoC: dt-bindings: qcom,sm8250: Add QCS6490 RubikPi3 sound card Hongyang Zhao
2026-06-06 23:40 ` Dmitry Baryshkov
2026-06-06 18:58 ` [PATCH 3/5] ASoC: qcom: qdsp6: q6prm: add the missing MCLK clock IDs Hongyang Zhao
2026-06-06 18:58 ` [PATCH 4/5] ASoC: qcom: sc8280xp: Add per-card data Hongyang Zhao
2026-06-06 21:28 ` sashiko-bot [this message]
2026-06-06 18:58 ` [PATCH 5/5] arm64: dts: qcom: qcs6490-rubikpi3: Add audio support Hongyang Zhao
2026-06-06 21:33 ` 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=20260606212806.ECF611F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hongyang.zhao@thundersoft.com \
--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