Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: broonie@kernel.org
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@opensource.cirrus.com
Subject: [PATCH 0/2] firmware: cs_dsp: Remove need for clients to supply dummy cs_dsp_client_ops
Date: Fri, 28 Nov 2025 10:21:30 +0000	[thread overview]
Message-ID: <20251128102132.1575177-1-rf@opensource.cirrus.com> (raw)

Clients of cs_dsp can provide optional callback function pointers, in
a struct cs_dsp_client_ops. The client had to provide a pointer to a
struct even if it didn't implement any of the callbacks.

Commit 1 in this series changes that so the client doesn't have to
provide a dummy struct.

Commit 2 adds kunit tests cases for this.

Richard Fitzgerald (2):
  firmware: cs_dsp: Don't require client to provide a struct
    cs_dsp_client_ops
  firmware: cs_dsp: Add test cases for client_ops == NULL

 drivers/firmware/cirrus/cs_dsp.c                     | 6 ++++++
 drivers/firmware/cirrus/test/cs_dsp_test_callbacks.c | 1 +
 2 files changed, 7 insertions(+)

-- 
2.47.3


             reply	other threads:[~2025-11-28 10:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-28 10:21 Richard Fitzgerald [this message]
2025-11-28 10:21 ` [PATCH 1/2] firmware: cs_dsp: Don't require client to provide a struct cs_dsp_client_ops Richard Fitzgerald
2025-11-28 10:21 ` [PATCH 2/2] firmware: cs_dsp: Add test cases for client_ops == NULL Richard Fitzgerald
2025-11-29  1:41 ` [PATCH 0/2] firmware: cs_dsp: Remove need for clients to supply dummy cs_dsp_client_ops 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=20251128102132.1575177-1-rf@opensource.cirrus.com \
    --to=rf@opensource.cirrus.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.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