From: sashiko-bot@kernel.org
To: "Bard Liao" <yung-chuan.liao@linux.intel.com>,
linux-sound@vger.kernel.org
Subject: Re: [PATCH v3 4/5] soundwire: Include the current stream when preparing again
Date: Thu, 12 Nov 2026 14:42:00 +0000 [thread overview]
Message-ID: <sashiko-outbox-211366@kernel.org> (raw)
In-Reply-To: <20261112141905.1372770-5-yung-chuan.liao@linux.intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] soundwire: missing Fixes trailers for DEPREPARED stream filter
commits
--
commit 0e099f6ac5f748061c8ae06b3d0b581ba6e28f1f
Author: Bard Liao <yung-chuan.liao@linux.intel.com>
> soundwire: Include the current stream when preparing again
>
> sdw_prepare_stream() accepts a stream in the DEPREPARED state without
> changing its state before parameter computation. However, the generic
> allocator excludes DEPREPARED streams from rate groups and port
> computation, and only includes a CONFIGURED current stream in group
> payload calculations.
>
> Consequently, preparing an existing stream again can reserve bandwidth
> without computing the corresponding transport parameters. The filters
> need to distinguish preparing that stream again from depreparing it.
>
> Pass the prepare context through the group and port helpers. Include
> the current stream during prepare even when it is still DEPREPARED,
> while preserving the filtering of all other runtimes and the behavior
> during deprepare. This supports preparing again without temporarily
> changing stream state.
>
> Signed-off-by: Bard Liao <yung-chuan.liao@linux.intel.com>
> Reviewed-by: Péter Ujfalusi <peter.ujfalusi@linux.intel.com>
[Severity: Low]
This fixes a bug where re-preparing a DEPREPARED stream skips transport and
port parameter computation due to state filters introduced in earlier
commits. Should this include Fixes tags for the commits that added those
checks:
Fixes: fdd1faeeec14 ("soundwire: generic_bandwidth_allocation: skip DEPREPARED streams")
Fixes: 25befdf32aa4 ("soundwire: generic_bandwidth_allocation: count the bandwidth of active streams only")
Fixes: 62ada17a6217 ("soundwire: only compute port params in specific stream states")
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261112141905.1372770-1-yung-chuan.liao@linux.intel.com?part=4
next prev parent reply other threads:[~2026-11-12 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 14:19 [PATCH v3 0/5] soundwire: Fix bandwidth leak in multi-link aggregation failure Bard Liao
2026-11-12 14:19 ` [PATCH v3 1/5] soundwire: move lane bandwidth into bus params Bard Liao
2026-11-12 14:19 ` [PATCH v3 2/5] soundwire: Pass prepare context to parameter computation Bard Liao
2026-11-12 14:19 ` [PATCH v3 3/5] soundwire: Select the correct runtime for lane allocation Bard Liao
2026-11-12 14:19 ` [PATCH v3 4/5] soundwire: Include the current stream when preparing again Bard Liao
2026-11-12 14:42 ` sashiko-bot [this message]
2026-11-12 14:19 ` [PATCH v3 5/5] soundwire: stream: Fix bandwidth leak in multi-link aggregation failure Bard Liao
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=sashiko-outbox-211366@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--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