From: sashiko-bot@kernel.org
To: "Mohammad Rafi Shaik" <mohammad.rafi.shaik@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 5/5] ASoC: qcom: sc8280xp: Add Nord sound card support
Date: Thu, 08 Oct 2026 11:15:50 +0000 [thread overview]
Message-ID: <sashiko-outbox-164081@kernel.org> (raw)
In-Reply-To: <20261008-nord-asoc-driver-support-v2-v2-5-0b6f7e94060d@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] ASoC: qcom: Codec internal enums hardcoded in machine driver
--
commit 2721d92879dd4f31b8adcd325b2322e0930198bc
Author: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
ASoC: qcom: sc8280xp: Add Nord sound card support
This commit adds support for the Nord Ride and RRD sound cards by
introducing the qcom,nord-sndcard compatible and associated
platform-specific data. It configures the codec DAI format for DSP_A
operation and enables MI2S bit clock handling. It also adds a
platform-specific sound card initialization callback to configure the
ADAU1979 capture codec to use LRCLK as its system clock source.
> diff --git a/sound/soc/qcom/sc8280xp.c b/sound/soc/qcom/sc8280xp.c
> index b5d367486d56a..a759ae9511b6b 100644
> --- a/sound/soc/qcom/sc8280xp.c
> +++ b/sound/soc/qcom/sc8280xp.c
> @@ -25,6 +25,10 @@
> #define I2S_BIT_RATE(rate, channels, format) \
> ((rate) * (channels) * (format))
>
> +#define ADAU1977_SYSCLK 0
> +#define ADAU1977_SYSCLK_SRC_MCLK 0
> +#define ADAU1977_SYSCLK_SRC_LRCLK 1
[Severity: Low]
Does duplicating these magic values from the codec driver create a brittle
dependency?
When nord_snd_init() passes these hardcoded macros to
snd_soc_component_set_sysclk(), it relies on the internal integer values of
the ADAU1977/ADAU1979 codec's clock definitions matching these definitions.
If the codec driver maintainers change the enum values, the machine driver
will silently configure the wrong clock and cause audio capture failures.
Could these identifiers be exposed through a shared header in include/sound/
instead of being duplicated in the machine driver?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261008-nord-asoc-driver-support-v2-v2-0-0b6f7e94060d@oss.qualcomm.com?part=5
next prev parent reply other threads:[~2026-10-08 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 11:06 [PATCH v2 0/5] ASoC: qcom: Add Nord audio support Mohammad Rafi Shaik
2026-10-08 11:06 ` [PATCH v2 1/5] ASoC: dt-bindings: ti,pcm1681: Document the optional SCK clock Mohammad Rafi Shaik
2026-10-08 11:06 ` [PATCH v2 2/5] ASoC: codec: pcm1681: Add optional SCK clock and runtime PM support Mohammad Rafi Shaik
2026-10-08 11:13 ` sashiko-bot
2026-10-08 11:06 ` [PATCH v2 3/5] ASoC: codec: pcm1681: Add TDM support Mohammad Rafi Shaik
2026-10-08 11:06 ` [PATCH v2 4/5] ASoC: dt-bindings: qcom,sm8250: Add Nord sound card Mohammad Rafi Shaik
2026-10-08 19:48 ` Rob Herring (Arm)
2026-10-08 11:06 ` [PATCH v2 5/5] ASoC: qcom: sc8280xp: Add Nord sound card support Mohammad Rafi Shaik
2026-10-08 11:15 ` sashiko-bot [this message]
2026-10-09 1:50 ` [PATCH v2 0/5] ASoC: qcom: Add Nord audio support Shawn Guo
2026-10-09 6:18 ` Mohammad Rafi Shaik
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-164081@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=mohammad.rafi.shaik@oss.qualcomm.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