From: Vinod Koul <vkoul@kernel.org>
To: linux-sound@vger.kernel.org,
Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
pierre-louis.bossart@linux.dev, peter.ujfalusi@linux.intel.com,
bard.liao@intel.com
Subject: Re: [PATCH v2 0/3] soundwire: bus: re-enable CLOCK_STOP_MODE1 support
Date: Tue, 08 Sep 2026 19:28:38 +0530 [thread overview]
Message-ID: <178887591841.2104350.3095665702238521740.b4-ty@kernel.org> (raw)
In-Reply-To: <20260901030311.232823-1-yung-chuan.liao@linux.intel.com>
On Tue, 01 Sep 2026 11:03:08 +0800, Bard Liao wrote:
> Add CLOCK_STOP_MODE1 back to allow the peripheral to utilize it when
> the clock is stopped.
> This mode is designed for power-sensitive devices as it enables a deeper
> power-saving state, although it does not retain the peripheral's state
> during the clock stop.
>
> v2:
> - check slave->probed before looking at the driver to avoid NULL pointer
> dereference.
> - add wake_enable parameter to stop_bus ops to stop the clock but keep the
> bus unwakeable during system suspend.
>
> [...]
Applied, thanks!
[1/3] soundwire: bus: add CLOCK_STOP_MODE1 support back
commit: 267665f8a3d7a17c5012f85b068d4e11f83432c1
[2/3] soundwire: Intel: add wake_enable parameter to stop_bus ops
commit: 8c1e69e322a9757f596242bdd004e76e30181869
[3/3] soundwire: Intel: stop sdw clock in system suspend
commit: 90b63b309fd6c0f192337659e73e3047a67df99f
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-09-08 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 3:03 Bard Liao
2026-09-01 3:03 ` [PATCH v2 1/3] soundwire: bus: add CLOCK_STOP_MODE1 support back Bard Liao
2026-09-01 3:03 ` [PATCH v2 2/3] soundwire: Intel: add wake_enable parameter to stop_bus ops Bard Liao
2026-09-01 3:03 ` [PATCH v2 3/3] soundwire: Intel: stop sdw clock in system suspend Bard Liao
2026-09-04 7:25 ` [PATCH v2 0/3] soundwire: bus: re-enable CLOCK_STOP_MODE1 support Pierre-Louis Bossart
2026-09-08 13:58 ` Vinod Koul [this message]
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=178887591841.2104350.3095665702238521740.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=bard.liao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=vinod.koul@linaro.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
all inboxes | Powered by JetHome®