From: sashiko-bot@kernel.org
To: "Harendra Gautam" <harendra.gautam@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v7 05/10] ASoC: soc-core: Add snd_soc_of_xlate_dai_name() generic helper
Date: Wed, 23 Sep 2026 07:00:44 +0000 [thread overview]
Message-ID: <20260923070044.DED9D1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260923-b4-qaif-shikra-audio-v7-5-d5b6f056568e@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] soc: build error due to implicit snd_soc_dai_name() declaration
--
commit b16b9f309d3d8ca044a5a756ee464aa98d0ba452
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 snd_soc_of_xlate_dai_name() to soc-core.c
for ASoC CPU DAI drivers. It resolves a sound-dai phandle argument to a DAI
name by iterating the component's DAI list and matching the DAI ID.
> diff --git a/sound/soc/soc-core.c b/sound/soc/soc-core.c
> index b9c70268d49fe..fc3f1606f0837 100644
> --- a/sound/soc/soc-core.c
> +++ b/sound/soc/soc-core.c
[ ... ]
> +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(dai);
[Severity: Low]
Does this code cause a build failure due to an implicit declaration of
snd_soc_dai_name()? It appears snd_soc_dai_name() does not exist in the
codebase. Should this use snd_soc_dai_name_get(dai) instead to successfully
retrieve the DAI name and avoid an invalid assignment?
> + return 0;
> + }
> + }
> +
> + return -EINVAL;
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260923-b4-qaif-shikra-audio-v7-0-d5b6f056568e@oss.qualcomm.com?part=5
next prev parent reply other threads:[~2026-09-23 7:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 6:48 [PATCH v7 00/10] ASoC: qcom: Add QAIF driver for Shikra audio platform Harendra Gautam
2026-09-23 6:48 ` [PATCH v7 01/10] ASoC: dt-bindings: qcom,shikra-qaif-cpu: Add binding Harendra Gautam
2026-09-23 6:59 ` sashiko-bot
2026-09-23 6:48 ` [PATCH v7 02/10] ASoC: qcom: Add QAIF shared data structures and variant interface Harendra Gautam
2026-09-23 6:59 ` sashiko-bot
2026-09-23 9:29 ` Mark Brown
2026-09-28 9:11 ` Harendra Gautam
2026-09-23 6:48 ` [PATCH v7 03/10] ASoC: qcom: Add QAIF hardware register map Harendra Gautam
2026-09-23 7:00 ` sashiko-bot
2026-09-23 6:48 ` [PATCH v7 04/10] ASoC: qcom: Add QAIF CPU DAI ops, regmap, DT parsing and platform init Harendra Gautam
2026-09-23 7:02 ` sashiko-bot
2026-09-23 9:41 ` Mark Brown
2026-09-28 9:38 ` Harendra Gautam
2026-09-28 12:17 ` Harendra Gautam
2026-09-23 6:48 ` [PATCH v7 05/10] ASoC: soc-core: Add snd_soc_of_xlate_dai_name() generic helper Harendra Gautam
2026-09-23 7:00 ` sashiko-bot [this message]
2026-09-23 6:48 ` [PATCH v7 06/10] ASoC: qcom: Switch lpass-cpu and qaif-cpu to snd_soc_of_xlate_dai_name() Harendra Gautam
2026-09-24 10:32 ` Ajay Kumar Nandam
2026-09-23 6:48 ` [PATCH v7 07/10] ASoC: qcom: Add QAIF PCM operations Harendra Gautam
2026-09-23 7:03 ` sashiko-bot
2026-09-23 9:45 ` Mark Brown
2026-09-28 9:06 ` Harendra Gautam
2026-09-23 6:48 ` [PATCH v7 08/10] ASoC: qcom: Add QAIF IRQ handling and platform register Harendra Gautam
2026-09-23 7:04 ` sashiko-bot
2026-09-23 6:48 ` [PATCH v7 09/10] ASoC: qcom: Add Shikra QAIF support Harendra Gautam
2026-09-23 7:09 ` sashiko-bot
2026-09-23 6:48 ` [PATCH v7 10/10] MAINTAINERS: Add Qualcomm QAIF driver entry Harendra Gautam
2026-09-23 9:27 ` [PATCH v7 00/10] ASoC: qcom: Add QAIF driver for Shikra audio platform Mark Brown
2026-09-28 5:44 ` 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=20260923070044.DED9D1F000FF@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