From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <pierre-louis.bossart@linux.dev>,
<yung-chuan.liao@linux.intel.com>,
<peter.ujfalusi@linux.intel.com>, <linux-sound@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>
Subject: [PATCH 3/6] ASoC: SDCA: Allow naming of imp def controls
Date: Wed, 12 Mar 2025 17:22:02 +0000 [thread overview]
Message-ID: <20250312172205.4152686-4-ckeepax@opensource.cirrus.com> (raw)
In-Reply-To: <20250312172205.4152686-1-ckeepax@opensource.cirrus.com>
Implementation defined controls will not be present in the large list of
known controls for SDCA. The driver should not return an error for these,
because it is perfectly legal to have implementation defined controls.
Update the handling to instead generate a generic name.
Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
---
sound/soc/sdca/sdca_functions.c | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/sound/soc/sdca/sdca_functions.c b/sound/soc/sdca/sdca_functions.c
index 4ee98d8fe89ed..1e36dd20d7abf 100644
--- a/sound/soc/sdca/sdca_functions.c
+++ b/sound/soc/sdca/sdca_functions.c
@@ -241,7 +241,8 @@ static int find_sdca_init_table(struct device *dev,
return 0;
}
-static const char *find_sdca_control_label(const struct sdca_entity *entity,
+static const char *find_sdca_control_label(struct device *dev,
+ const struct sdca_entity *entity,
const struct sdca_control *control)
{
switch (SDCA_CTL_TYPE(entity->type, control->sel)) {
@@ -530,7 +531,7 @@ static const char *find_sdca_control_label(const struct sdca_entity *entity,
case SDCA_CTL_TYPE_S(ENTITY_0, DEVICE_SDCA_VERSION):
return SDCA_CTL_DEVICE_SDCA_VERSION_NAME;
default:
- return NULL;
+ return devm_kasprintf(dev, GFP_KERNEL, "Imp-Def %#x", control->sel);
}
}
@@ -739,12 +740,9 @@ static int find_sdca_entity_control(struct device *dev, struct sdca_entity *enti
if (!ret)
control->interrupt_position = tmp;
- control->label = find_sdca_control_label(entity, control);
- if (!control->label) {
- dev_err(dev, "%s: control %#x: name not found\n",
- entity->label, control->sel);
- return -EINVAL;
- }
+ control->label = find_sdca_control_label(dev, entity, control);
+ if (!control->label)
+ return -ENOMEM;
control->nbits = find_sdca_control_bits(entity, control);
--
2.39.5
next prev parent reply other threads:[~2025-03-12 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 17:21 [PATCH 0/6] Some minor SDCA preparation Charles Keepax
2025-03-12 17:22 ` [PATCH 1/6] ASoC: SDCA: Tidy up initialization write parsing Charles Keepax
2025-03-12 17:22 ` [PATCH 2/6] ASoC: SDCA: Use __free() to manage local buffers Charles Keepax
2025-03-12 17:22 ` Charles Keepax [this message]
2025-03-12 17:22 ` [PATCH 4/6] ASoC: SDCA: Add type flag for Controls Charles Keepax
2025-03-12 17:22 ` [PATCH 5/6] ASoC: SDCA: Add SDCA Control Range data access helper Charles Keepax
2025-03-12 17:22 ` [PATCH 6/6] ASoC: SDCA: Add support for GE Entity properties Charles Keepax
2025-03-17 21:54 ` [PATCH 0/6] Some minor SDCA preparation 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=20250312172205.4152686-4-ckeepax@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=yung-chuan.liao@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox