mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: HyeongJun An <sammiee5311@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: HyeongJun An <sammiee5311@gmail.com>,
	Vinod Koul <vkoul@kernel.org>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
	Srinivas Kandagatla <srini@kernel.org>,
	linux-sound@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/10] soundwire: Fix Critical and High issues reported by Sashiko
Date: Sat,  7 Nov 2026 18:41:40 +0900	[thread overview]
Message-ID: <20261107094140.3951536-1-sammiee5311@gmail.com> (raw)
In-Reply-To: <20261103095445.81414-1-lee@kernel.org>

On a Dell Latitude 9420 (Tiger Lake, SOF IPC3, sof_sdw with rt711-sdca
on link 0, two rt1316 on links 1 and 2 that are aggregated into one
Speaker stream, and rt714 on link 3), I tested this series on top of
soundwire next at commit afd88e7ad781. Only patches 1-4 run on this
machine. The intel_ace2x and qcom patches are not exercised here.

With and without the series:
- all four peripherals attach at boot
- playback and capture work on every endpoint
- 40 start/stop cycles of the multi-link Speaker stream (10 of them
  after the links had runtime suspended), all links streaming at the
  same time, and Jack Out start/stop while Speaker was playing all
  passed
- ALSA pcm-test: 24 pass, 0 fail
- the dev-properties, dp0 and dpN sysfs attributes of all four
  peripherals read back identical (the words arrays are empty on these
  codecs, so only the trailing newline goes through the changed code)

With the series, s2idle with Speaker playback and Microphone capture
running: all four peripherals were attached again after resume, both
streams continued after aplay/arecord re-prepared them, and playback and
capture on every endpoint still worked. There were no SoundWire or SOF
kernel messages. I did not run the same s2idle test without the series.

These runs only take the normal paths, so the failure cases that
patches 3 and 4 guard against were not hit.

I ran these with Claude Code (Claude Opus 5.5) on the laptop.

I am sending Tested-by on patches 1-4 only, in replies to those
patches.

  parent reply	other threads:[~2026-11-07  9:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03  9:53 Lee Jones
2026-11-03  9:53 ` [PATCH v2 01/10] soundwire: bus: Hold bus_lock when looking up slave devices Lee Jones
2026-11-07  9:41   ` HyeongJun An
2026-11-03  9:53 ` [PATCH v2 02/10] soundwire: sysfs: Use sysfs_emit_at() in array show callbacks Lee Jones
2026-11-07  9:42   ` HyeongJun An
2026-11-03  9:53 ` [PATCH v2 03/10] soundwire: stream: Prevent m_rt_count underflow in sdw_stream_remove_master() Lee Jones
2026-11-07  9:42   ` HyeongJun An
2026-11-03  9:53 ` [PATCH v2 04/10] soundwire: stream: Clean up allocated runtime resources on config failure Lee Jones
2026-11-07  9:42   ` HyeongJun An
2026-11-03  9:53 ` [PATCH v2 05/10] soundwire: intel_ace2x: Protect bus.bpt_stream with bus_lock Lee Jones
2026-11-03  9:53 ` [PATCH v2 06/10] soundwire: qcom: Prevent pconfig buffer overflow in qcom_swrm_stream_alloc_ports() Lee Jones
2026-11-03  9:53 ` [PATCH v2 07/10] soundwire: qcom: Disable runtime PM and avoid clock underflow in qcom_swrm_remove() Lee Jones
2026-11-03  9:53 ` [PATCH v2 08/10] soundwire: qcom: Check clk_prepare_enable() return value Lee Jones
2026-11-03  9:53 ` [PATCH v2 09/10] soundwire: qcom: Serialise ctrl->intr_mask updates Lee Jones
2026-11-03  9:53 ` [PATCH v2 10/10] soundwire: qcom: Prevent stale broadcast IRQ from completing subsequent command Lee Jones
2026-11-07  9:41 ` HyeongJun An [this message]
2026-11-10  9:04   ` [PATCH v2 00/10] soundwire: Fix Critical and High issues reported by Sashiko Lee Jones

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=20261107094140.3951536-1-sammiee5311@gmail.com \
    --to=sammiee5311@gmail.com \
    --cc=lee@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=srini@kernel.org \
    --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

all inboxes | Powered by JetHome®