From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Charles Keepax <ckeepax@opensource.cirrus.com>, broonie@kernel.org
Cc: lgirdwood@gmail.com, vkoul@kernel.org,
yung-chuan.liao@linux.intel.com, peter.ujfalusi@linux.intel.com,
shumingf@realtek.com, linux-sound@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH v3 0/4] SDCA System Suspend Support
Date: Tue, 13 Jan 2026 22:29:51 +0100 [thread overview]
Message-ID: <d986d4a8-1686-4020-921e-e484808d029f@linux.dev> (raw)
In-Reply-To: <20260109145206.3456151-1-ckeepax@opensource.cirrus.com>
On 1/9/26 15:52, Charles Keepax wrote:
> Add support for system suspend into the class driver, now split
> out into a separate patch chain.
>
> Where we got to on the previous discussion, was we don't currently
> have any parts requiring download on runtime resume, doing so
> will add noticeable delay to the runtime resume, and we are not
> blocking someone from adding support for firmware download on
> runtime resume in the future. Also as runtime resume is really
> a kernel concept and power rails are primarily controlled by
> ACPI it is quite unlikely anyone will actually power down the
> part on a runtime suspend anyway. So this version of the chain
> still only downloads firmware on probe and system resume.
LGTM, thanks Charles
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
> Changes since v2:
> - Update some error message capitalisation.
> - Update some kernel doc.
> - Add a runtime_get to ensure force resume runs the runtime resume.
> - Correct detection of system suspend in FDL IRQ.
>
> Changes since v1:
> - Update SDCA IRQ enable/disable API to be more clear.
>
> Charles Keepax (4):
> ASoC: SDCA: Add SDCA IRQ enable/disable helpers
> ASoC: SDCA: Add basic system suspend support
> ASoC: SDCA: Device boot into the system suspend process
> ASoC: SDCA: Add lock to serialise the Function initialisation
>
> include/sound/sdca_interrupts.h | 7 ++
> sound/soc/sdca/sdca_class.c | 34 ++++++++
> sound/soc/sdca/sdca_class.h | 2 +
> sound/soc/sdca/sdca_class_function.c | 126 ++++++++++++++++++++++-----
> sound/soc/sdca/sdca_interrupts.c | 93 ++++++++++++++++++--
> 5 files changed, 236 insertions(+), 26 deletions(-)
>
next prev parent reply other threads:[~2026-01-13 22:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 14:52 [PATCH v3 0/4] SDCA System Suspend Support Charles Keepax
2026-01-09 14:52 ` [PATCH v3 1/4] ASoC: SDCA: Add SDCA IRQ enable/disable helpers Charles Keepax
2026-01-09 14:52 ` [PATCH v3 2/4] ASoC: SDCA: Add basic system suspend support Charles Keepax
2026-01-09 14:52 ` [PATCH v3 3/4] ASoC: SDCA: Device boot into the system suspend process Charles Keepax
2026-01-09 14:52 ` [PATCH v3 4/4] ASoC: SDCA: Add lock to serialise the Function initialisation Charles Keepax
2026-01-13 21:29 ` Pierre-Louis Bossart [this message]
2026-01-14 21:36 ` [PATCH v3 0/4] SDCA System Suspend Support 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=d986d4a8-1686-4020-921e-e484808d029f@linux.dev \
--to=pierre-louis.bossart@linux.dev \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=shumingf@realtek.com \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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