From: sashiko-bot@kernel.org
To: "Harendra Gautam" <harendra.gautam@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v6 05/10] ASoC: soc-core: Add snd_soc_of_xlate_dai_name() generic helper
Date: Fri, 11 Sep 2026 09:32:43 +0000 [thread overview]
Message-ID: <20260911093243.EA0B91F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260911-b4-qaif-shikra-audio-v6-5-e9addb358201@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Call to non-existent function `snd_soc_dai_name_get` causes a build failure.
--
commit d2ced32400830e456cc64d54ef5e9807fdbf58e6
Author: Harendra Gautam <harendra.gautam@oss.qualcomm.com>
ASoC: soc-core: Add snd_soc_of_xlate_dai_name() generic helper
This commit adds a generic helper to resolve a sound-dai phandle argument
to a DAI name. It iterates over a component's DAI list and matches by ID.
> diff --git a/sound/soc/soc-core.c b/sound/soc/soc-core.c
> index 06167a1985912..0c868bccd3b43 100644
> --- a/sound/soc/soc-core.c
> +++ b/sound/soc/soc-core.c
[ ... ]
> @@ -2906,6 +2906,39 @@ int snd_soc_of_parse_tdm_slot(struct device_node *np,
> +int snd_soc_of_xlate_dai_name(struct snd_soc_component *component,
> + const struct of_phandle_args *args,
> + const char **dai_name)
> +{
> + struct snd_soc_dai *dai;
> + int id;
> +
> + if (args->args_count != 1)
> + return -EINVAL;
> +
> + id = args->args[0];
> +
> + for_each_component_dais(component, dai) {
> + if (dai->driver->id == id) {
> + *dai_name = snd_soc_dai_name_get(dai);
[Severity: Low]
Does this cause a build failure? It looks like snd_soc_dai_name_get() is a
typo for snd_soc_dai_name(), which will result in an undefined reference or
implicit function declaration error when compiling sound/soc/soc-core.o.
> + return 0;
> + }
> + }
> +
> + return -EINVAL;
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260911-b4-qaif-shikra-audio-v6-0-e9addb358201@oss.qualcomm.com?part=5
next prev parent reply other threads:[~2026-09-11 9:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 9:17 [PATCH v6 00/10] ASoC: qcom: Add QAIF driver for Shikra audio platform Harendra Gautam
2026-09-11 9:17 ` [PATCH v6 01/10] ASoC: dt-bindings: qcom,shikra-qaif-cpu: Add binding Harendra Gautam
2026-09-11 9:17 ` [PATCH v6 02/10] ASoC: qcom: Add QAIF shared data structures and variant interface Harendra Gautam
2026-09-11 9:17 ` [PATCH v6 03/10] ASoC: qcom: Add QAIF hardware register map Harendra Gautam
2026-09-11 9:34 ` sashiko-bot
2026-09-11 9:17 ` [PATCH v6 04/10] ASoC: qcom: Add QAIF CPU DAI ops, regmap, DT parsing and platform init Harendra Gautam
2026-09-11 9:17 ` [PATCH v6 05/10] ASoC: soc-core: Add snd_soc_of_xlate_dai_name() generic helper Harendra Gautam
2026-09-11 9:32 ` sashiko-bot [this message]
2026-09-11 9:17 ` [PATCH v6 06/10] ASoC: qcom: Switch lpass-cpu and qaif-cpu to snd_soc_of_xlate_dai_name() Harendra Gautam
2026-09-11 9:40 ` sashiko-bot
2026-09-11 9:17 ` [PATCH v6 07/10] ASoC: qcom: Add QAIF PCM operations Harendra Gautam
2026-09-11 9:39 ` sashiko-bot
2026-09-11 9:17 ` [PATCH v6 08/10] ASoC: qcom: Add QAIF IRQ handling and platform register Harendra Gautam
2026-09-11 9:40 ` sashiko-bot
2026-09-11 9:17 ` [PATCH v6 09/10] ASoC: qcom: Add Shikra QAIF support Harendra Gautam
2026-09-11 9:17 ` [PATCH v6 10/10] MAINTAINERS: Add Qualcomm QAIF driver entry Harendra Gautam
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=20260911093243.EA0B91F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=harendra.gautam@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