From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: yung-chuan.liao@linux.intel.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH] ASoC: cs35l56: Support clock stop mode 1 if enabled in ACPI
Date: Wed, 11 Mar 2026 18:56:59 +0000 [thread overview]
Message-ID: <177325541965.227645.3283429879588032608.b4-ty@kernel.org> (raw)
In-Reply-To: <20260311142153.2201761-1-rf@opensource.cirrus.com>
On Wed, 11 Mar 2026 14:21:53 +0000, Richard Fitzgerald wrote:
> Report the ability to support SoundWire clock-stop mode 1 if this is
> enabled in ACPI. Mode 1 allows the device to lose state, so it can
> reduce power consumption in clock-stop. Also add the necessary
> handling to wait for re-enumeration on resume.
>
> This does not use sdw_slave_read_prop(), because that also fills in
> other properties from ACPI that were not previously set by the driver
> and this has been observed to break some systems. Instead, the
> "mipi-sdw-clock-stop-mode1-supported" property is checked directly.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: cs35l56: Support clock stop mode 1 if enabled in ACPI
commit: 48863104d2e1ea70a68cbd8d87c0d75270f3c6e5
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
next prev parent reply other threads:[~2026-03-11 18:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 14:21 Richard Fitzgerald
2026-03-11 15:03 ` Mark Brown
2026-03-11 15:17 ` Richard Fitzgerald
2026-03-11 15:30 ` Mark Brown
2026-03-11 15:34 ` Richard Fitzgerald
2026-03-11 15:50 ` Mark Brown
2026-03-11 15:58 ` Richard Fitzgerald
2026-03-11 16:09 ` Mark Brown
2026-03-11 18:56 ` Mark Brown [this message]
2026-03-14 21:58 ` 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=177325541965.227645.3283429879588032608.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--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
all inboxes | Powered by JetHome®