From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: <broonie@kernel.org>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>
Subject: [PATCH 0/5] ASoC: cs35l56: Bugfixes
Date: Tue, 8 Aug 2023 17:46:57 +0100 [thread overview]
Message-ID: <20230808164702.21272-1-rf@opensource.cirrus.com> (raw)
Miscellaneous bugfixes for the cs35l56 codec driver.
Richard Fitzgerald (3):
ASoC: cs35l56: Avoid uninitialized variable in
cs35l56_set_asp_slot_positions()
ASoC: cs35l56: Don't rely on GPIOD_OUT_LOW to set RESET initially low
ASoC: cs35l56: Wait for control port ready during system-resume
Simon Trimmer (2):
ASoC: wm_adsp: Expose the DSP power down actions as
wm_adsp_power_down()
ASoC: cs35l56: Call wm_adsp_power_down() before reloading firmware
sound/soc/codecs/cs35l56.c | 33 +++++++++++++++++----------------
sound/soc/codecs/wm_adsp.c | 8 +++++++-
sound/soc/codecs/wm_adsp.h | 1 +
3 files changed, 25 insertions(+), 17 deletions(-)
--
2.30.2
next reply other threads:[~2023-08-08 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 16:46 Richard Fitzgerald [this message]
2023-08-08 16:46 ` [PATCH 1/5] ASoC: cs35l56: Avoid uninitialized variable in cs35l56_set_asp_slot_positions() Richard Fitzgerald
2023-08-08 16:46 ` [PATCH 2/5] ASoC: cs35l56: Don't rely on GPIOD_OUT_LOW to set RESET initially low Richard Fitzgerald
2023-08-08 16:47 ` [PATCH 3/5] ASoC: cs35l56: Wait for control port ready during system-resume Richard Fitzgerald
2023-08-08 16:47 ` [PATCH 4/5] ASoC: wm_adsp: Expose the DSP power down actions as wm_adsp_power_down() Richard Fitzgerald
2023-08-08 16:47 ` [PATCH 5/5] ASoC: cs35l56: Call wm_adsp_power_down() before reloading firmware Richard Fitzgerald
2023-08-09 17:26 ` [PATCH 0/5] ASoC: cs35l56: Bugfixes 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=20230808164702.21272-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=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;
as well as URLs for NNTP newsgroup(s).