From: Khaled Saleh <khaled.saleh.req@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, greybus-dev@lists.linaro.org,
Khaled Saleh <khaled.saleh.req@gmail.com>
Subject: [PATCH] staging: greybus: split gb_audio_gb_get_topology() into helper functions
Date: Mon, 22 Dec 2025 18:15:17 +0200 [thread overview]
Message-ID: <20251222161517.6123-1-khaled.saleh.req@gmail.com> (raw)
The gb_audio_gb_get_topology() function performs multiple distinct
operations: retrieving the topology size, allocating the topology buffer,
and fetching the topology data. A TODO comment in the file notes that
this logic should be split into separate calls.
Introduce helper functions for each step and update
gb_audio_gb_get_topology() to use them.
This improves readability and maintainability without changing behavior.
Signed-off-by: Khaled Saleh <khaled.saleh.req@gmail.com>
---
drivers/staging/greybus/audio_gb.c | 47 +++++++++++++++++++++++-------
1 file changed, 36 insertions(+), 11 deletions(-)
diff --git a/drivers/staging/greybus/audio_gb.c b/drivers/staging/greybus/audio_gb.c
index 9d8994fdb41a..0d5109ec14f6 100644
--- a/drivers/staging/greybus/audio_gb.c
+++ b/drivers/staging/greybus/audio_gb.c
@@ -9,36 +9,61 @@
#include "audio_codec.h"
/* TODO: Split into separate calls */
+static int gb_audio_topology_get_size(struct gb_connection *connection, u16 *size)
+{
+ struct gb_audio_get_topology_size_response resp;
+ int ret;
+
+ ret = gb_operation_sync(connection,
+ GB_AUDIO_TYPE_GET_TOPOLOGY_SIZE,
+ NULL, 0,
+ &resp, sizeof(resp));
+ if (ret)
+ return ret;
+
+ *size = le16_to_cpu(resp.size);
+
+ return 0;
+}
+
+static struct gb_audio_topology *gb_audio_topology_alloc(u16 size)
+{
+ if (size < sizeof(struct gb_audio_topology))
+ return NULL;
+
+ return kzalloc(size, GFP_KERNEL);
+}
+
+static int gb_audio_topology_fetch(struct gb_connection *connection,
+ struct gb_audio_topology *topo, u16 size)
+{
+ return gb_operation_sync(connection,
+ GB_AUDIO_TYPE_GET_TOPOLOGY,
+ NULL, 0,
+ topo, size);
+}
int gb_audio_gb_get_topology(struct gb_connection *connection,
struct gb_audio_topology **topology)
{
- struct gb_audio_get_topology_size_response size_resp;
struct gb_audio_topology *topo;
u16 size;
int ret;
- ret = gb_operation_sync(connection, GB_AUDIO_TYPE_GET_TOPOLOGY_SIZE,
- NULL, 0, &size_resp, sizeof(size_resp));
+ ret = gb_audio_topology_get_size(connection, &size);
if (ret)
return ret;
- size = le16_to_cpu(size_resp.size);
- if (size < sizeof(*topo))
- return -ENODATA;
-
- topo = kzalloc(size, GFP_KERNEL);
+ topo = gb_audio_topology_alloc(size);
if (!topo)
return -ENOMEM;
- ret = gb_operation_sync(connection, GB_AUDIO_TYPE_GET_TOPOLOGY, NULL, 0,
- topo, size);
+ ret = gb_audio_topology_fetch(connection, topo, size);
if (ret) {
kfree(topo);
return ret;
}
*topology = topo;
-
return 0;
}
EXPORT_SYMBOL_GPL(gb_audio_gb_get_topology);
--
2.43.0
next reply other threads:[~2025-12-22 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 16:15 Khaled Saleh [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-21 19:42 [PATCH] staging: greybus: split gb_audio_gb_get_topology() into helper functions Khaled Saleh
2025-12-22 6:23 ` Greg KH
2026-01-05 9:29 ` Dan Carpenter
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=20251222161517.6123-1-khaled.saleh.req@gmail.com \
--to=khaled.saleh.req@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=linux-staging@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