From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: <broonie@kernel.org>, <tiwai@suse.com>
Cc: <linux-sound@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>,
"Richard Fitzgerald" <rf@opensource.cirrus.com>
Subject: [PATCH 0/5] ALSA: cirrus: Tidy up of firmware control read/write
Date: Mon, 25 Mar 2024 11:31:22 +0000 [thread overview]
Message-ID: <20240325113127.112783-1-rf@opensource.cirrus.com> (raw)
This set of patches factors out some repeated code to clean up
firmware control read/write functions, and removes some redundant
control notification code.
Simon Trimmer (5):
firmware: cs_dsp: Add locked wrappers for coeff read and write
ASoC: wm_adsp: Use cs_dsp_coeff_lock_and_[read|write]_ctrl()
ALSA: hda: hda_cs_dsp_ctl: Use
cs_dsp_coeff_lock_and_[read|write]_ctrl()
ASoC: wm_adsp: Remove notification of driver write
ALSA: hda: hda_cs_dsp_ctl: Remove notification of driver write
drivers/firmware/cirrus/cs_dsp.c | 54 ++++++++++++++++++++++++++
include/linux/firmware/cirrus/cs_dsp.h | 4 ++
sound/pci/hda/hda_cs_dsp_ctl.c | 22 +----------
sound/soc/codecs/wm_adsp.c | 32 ++++-----------
4 files changed, 67 insertions(+), 45 deletions(-)
--
2.39.2
next reply other threads:[~2024-03-25 11:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 11:31 Richard Fitzgerald [this message]
2024-03-25 11:31 ` [PATCH 1/5] firmware: cs_dsp: Add locked wrappers for coeff read and write Richard Fitzgerald
2024-03-25 11:31 ` [PATCH 2/5] ASoC: wm_adsp: Use cs_dsp_coeff_lock_and_[read|write]_ctrl() Richard Fitzgerald
2024-03-25 11:31 ` [PATCH 3/5] ALSA: hda: hda_cs_dsp_ctl: " Richard Fitzgerald
2024-03-25 11:31 ` [PATCH 4/5] ASoC: wm_adsp: Remove notification of driver write Richard Fitzgerald
2024-03-25 11:31 ` [PATCH 5/5] ALSA: hda: hda_cs_dsp_ctl: " Richard Fitzgerald
2024-03-30 8:40 ` [PATCH 0/5] ALSA: cirrus: Tidy up of firmware control read/write Takashi Iwai
2024-04-01 9:32 ` Richard Fitzgerald
2024-04-01 11:46 ` Takashi Iwai
2024-04-03 21:46 ` 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=20240325113127.112783-1-rf@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.