From: sashiko-bot@kernel.org
To: "Sen Wang" <sen@ti.com>
Cc: conor+dt@kernel.org, krzk+dt@kernel.org,
devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 2/2] ASoC: simple-card-utils: support system-clock-id DT property
Date: Fri, 15 May 2026 16:37:38 +0000 [thread overview]
Message-ID: <20260515163739.5DDE2C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260515161358.1462453-3-sen@ti.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The commit introduces asymmetric sysclk configuration by failing to update `clk_id` in the shutdown path, leading to incorrect hardware states and resource leaks.
--
commit fb04cb3ea63c6e1c03c9835d2530dab5d343394b
Author: Sen Wang <sen@ti.com>
ASoC: simple-card-utils: support system-clock-id DT property
This commit adds an optional system-clock-id DT property to the cpu/codec
sub-nodes. It updates simple_util_parse_clk(), simple_util_hw_params(),
and simple_init_dai() to read and use this clock ID instead of hardcoding 0.
> diff --git a/sound/soc/generic/simple-card-utils.c b/sound/soc/generic/simple-card-utils.c
> index e5cb602fd2487..441f68df85220 100644
> --- a/sound/soc/generic/simple-card-utils.c
> +++ b/sound/soc/generic/simple-card-utils.c
[ ... ]
> @@ -506,14 +509,16 @@ int simple_util_hw_params(struct snd_pcm_substream *substream,
> /* CPU first */
> for_each_rtd_cpu_dais(rtd, i, sdai) {
> pdai = simple_props_to_dai_cpu(props, i);
> - ret = snd_soc_dai_set_sysclk(sdai, 0, mclk, pdai->clk_direction);
> + ret = snd_soc_dai_set_sysclk(sdai, pdai->clk_id,
> + mclk, pdai->clk_direction);
Does the teardown path in simple_util_shutdown() also need to be updated to
use clk_id?
It currently hardcodes 0 when disabling the clock:
sound/soc/generic/simple-card-utils.c:simple_util_shutdown() {
...
for_each_prop_dai_cpu(props, i, dai) {
struct snd_soc_dai *cpu_dai = snd_soc_rtd_to_cpu(rtd, i);
if (props->mclk_fs && !dai->clk_fixed && !snd_soc_dai_active(cpu_dai))
snd_soc_dai_set_sysclk(cpu_dai, 0, 0, dai->clk_direction);
...
}
If a device is configured with a non-zero system-clock-id, will the shutdown
path disable the wrong clock, leaving the intended clock running?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260515161358.1462453-1-sen@ti.com?part=2
next prev parent reply other threads:[~2026-05-15 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 16:13 [PATCH v2 0/2] ASoC: simple-card-utils: support system-clock-id DT property Sen Wang
2026-05-15 16:13 ` [PATCH v2 1/2] dt-bindings: sound: simple-card: add system-clock-id property Sen Wang
2026-05-16 9:54 ` Krzysztof Kozlowski
2026-05-16 10:17 ` Wang, Sen
2026-05-15 16:13 ` [PATCH v2 2/2] ASoC: simple-card-utils: support system-clock-id DT property Sen Wang
2026-05-15 16:37 ` sashiko-bot [this message]
2026-05-15 19:32 ` [PATCH v2 0/2] " Wang, Sen
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=20260515163739.5DDE2C2BCB0@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sen@ti.com \
/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.