From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Stefan Binding <sbinding@opensource.cirrus.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH v2 2/4] ASoC: codecs: wm_adsp: Allow wm_adsp to hibernate without stopping DSP
Date: Fri, 27 Feb 2026 09:58:41 +0000 [thread overview]
Message-ID: <322ccec2-3663-4034-acf8-71732154efba@opensource.cirrus.com> (raw)
In-Reply-To: <20260224161821.93365-3-sbinding@opensource.cirrus.com>
On 24/02/2026 4:18 pm, Stefan Binding wrote:
> Some parts do not stop the DSP core before runtime suspend, however,
> this leaves the DSP controls enabled and accessible whilst the part is
> suspended and the regmap is cache_only.
>
> Add new APIs to allow for the DSP to hibernate when the part is
> suspended, and the DSP is not shut down.
>
> Signed-off-by: Stefan Binding <sbinding@opensource.cirrus.com>
> ---
> sound/soc/codecs/wm_adsp.c | 6 ++++++
> sound/soc/codecs/wm_adsp.h | 1 +
> 2 files changed, 7 insertions(+)
Reviewed-by: Richard Fitzgerald <rf@opensource.cirrus.com>
next prev parent reply other threads:[~2026-02-27 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 16:18 [PATCH v2 0/4] Support wm_adsp hibernation for runtime suspend Stefan Binding
2026-02-24 16:18 ` [PATCH v2 1/4] firmware: cs_dsp: Add API to hibernate the DSP Stefan Binding
2026-02-27 9:58 ` Richard Fitzgerald
2026-02-24 16:18 ` [PATCH v2 2/4] ASoC: codecs: wm_adsp: Allow wm_adsp to hibernate without stopping DSP Stefan Binding
2026-02-27 9:58 ` Richard Fitzgerald [this message]
2026-02-24 16:18 ` [PATCH v2 3/4] ASoC: cs35l41: Hibernate wm_adsp on runtime suspend Stefan Binding
2026-02-24 16:18 ` [PATCH v2 4/4] ASoC: cs35l45: " Stefan Binding
2026-03-03 11:20 ` [PATCH v2 0/4] Support wm_adsp hibernation for " 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=322ccec2-3663-4034-acf8-71732154efba@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 \
--cc=sbinding@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
all inboxes | Powered by JetHome®