From: sashiko-bot@kernel.org
To: "David Heidelberg" <david@ixit.cz>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v4 1/8] ASoC: qcom: sdm845: Demystify TDM masks a bit
Date: Thu, 24 Sep 2026 13:34:58 +0000 [thread overview]
Message-ID: <20260924133458.E06821F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260924-pixel3-audio-v4-1-85b5d133aa5e@ixit.cz>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] ASoC: qcom: Incorrect RX suffix for microphone TDM masks
--
commit 58ae8e5a0a62726195e8056775500ca69d67f4a4
Author: David Heidelberg <david@ixit.cz>
ASoC: qcom: sdm845: Demystify TDM masks a bit
This commit describes the bits used for each RX/TX TDM mask instead of
using hardcoded hex values.
> diff --git a/sound/soc/qcom/sdm845.c b/sound/soc/qcom/sdm845.c
> index 6843ab8ba017e..0ce8265ab1c1f 100644
> --- a/sound/soc/qcom/sdm845.c
> +++ b/sound/soc/qcom/sdm845.c
> @@ -23,9 +23,14 @@
> #define DEFAULT_MCLK_RATE 24576000
> #define TDM_BCLK_RATE 6144000
> #define MI2S_BCLK_RATE 1536000
> -#define LEFT_SPK_TDM_TX_MASK 0x30
> -#define RIGHT_SPK_TDM_TX_MASK 0xC0
> -#define SPK_TDM_RX_MASK 0x03
> +#define LEFT_SPK_TDM_RX_MASK BIT(0)
> +#define RIGHT_SPK_TDM_RX_MASK BIT(1)
> +#define SPK_TDM_RX_MASK (LEFT_SPK_TDM_RX_MASK | RIGHT_SPK_TDM_RX_MASK)
> +#define MIC1_TDM_RX_MASK BIT(2)
> +#define MIC2_TDM_RX_MASK BIT(3)
> +#define MIC_TDM_RX_MASK (MIC1_TDM_RX_MASK | MIC2_TDM_RX_MASK)
[Severity: Low]
Are these microphone masks named correctly?
Microphones are capture devices that transmit data on the bus to the CPU,
meaning they utilize TX slots from the codec's perspective.
While the bitwise values remain correct and do not introduce a functional
regression, naming these slots with an RX suffix appears to contradict
their semantic role. This is particularly noticeable since the stated goal
of this patch is to clarify the masks by describing their RX/TX directions.
> +#define LEFT_SPK_TDM_TX_MASK (BIT(4) | BIT(5))
> +#define RIGHT_SPK_TDM_TX_MASK (BIT(6) | BIT(7))
> #define NUM_TDM_SLOTS 8
> #define SLIM_MAX_TX_PORTS 16
> #define SLIM_MAX_RX_PORTS 13
[ ... ]
> @@ -128,8 +133,10 @@ static int sdm845_tdm_snd_hw_params(struct snd_pcm_substream *substream,
> goto end;
> }
> } else {
> - ret = snd_soc_dai_set_tdm_slot(cpu_dai, 0xf, 0,
> - 8, slot_width);
> + ret = snd_soc_dai_set_tdm_slot(cpu_dai,
> + SPK_TDM_RX_MASK |
> + MIC_TDM_RX_MASK, 0,
> + NUM_TDM_SLOTS, slot_width);
[Severity: Low]
Does passing MIC_TDM_RX_MASK here create confusion in the capture path?
This passes the RX-suffixed microphone masks into the tx_mask parameter of
snd_soc_dai_set_tdm_slot() for the CPU capture DAI, since qdsp6 AFE expects
tx_mask for capture.
Could this be renamed to MIC_TDM_TX_MASK to properly reflect its transmit
role and align with the parameter it is passed into?
> if (ret < 0) {
> dev_err(rtd->dev, "%s: failed to set tdm slot, err:%d\n",
> __func__, ret);
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260924-pixel3-audio-v4-0-85b5d133aa5e@ixit.cz?part=1
next prev parent reply other threads:[~2026-09-24 13:35 UTC|newest]
Thread overview: 23+ 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 ` [PATCH v4 1/8] ASoC: qcom: sdm845: Demystify TDM masks a bit David Heidelberg via B4 Relay
2026-09-24 13:34 ` sashiko-bot [this message]
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-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-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-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: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:37 ` sashiko-bot
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: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 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=20260924133458.E06821F000FF@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox