From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Vijendar Mukunda <Vijendar.Mukunda@amd.com>, vkoul@kernel.org
Cc: broonie@kernel.org, alsa-devel@alsa-project.org,
yung-chuan.liao@linux.intel.com, Basavaraj.Hiregoudar@amd.com,
Sunil-kumar.Dommati@amd.com, venkataprasad.potturu@amd.com,
Syed.SabaKareem@amd.com, Mario.Limonciello@amd.com,
Richard.Gong@amd.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 02/10] soundwire: amd: cache ping slave status to avoid spurious disconnect on timeout
Date: Sun, 18 Oct 2026 18:41:18 +0200 [thread overview]
Message-ID: <94e1b390-903c-4a34-bd9e-9c128b6c1622@linux.dev> (raw)
In-Reply-To: <20261013085111.2009061-3-Vijendar.Mukunda@amd.com>
On 10/13/26 10:49, Vijendar Mukunda wrote:
> Add ping_slave_stat to struct amd_sdw_manager to cache the slave_stat
> from the last successful ping response. On timeout,
> amd_sdw_read_ping_status() returns the cached value (or 0 if no
> successful response yet) to avoid the spurious "no peripherals
> attached" warning from sdw_show_ping_status().
I read this description multiple times and I don't get
a) in what cases you'd get a timeout on a PING command?
and
b) why the cached value of the last ping is a relevant concealment?
You'd still get an error message on a timeout...Maybe this makes the log
"cleaner" but still there was an error in the first place.
> ping_slave_stat is initialised to U32_MAX in probe and reset to
> U32_MAX under msg_lock on entry to the POWER_OFF_MODE resume path,
> before any hardware step that can fail and return early, so that a
> partially-failed resume cannot leave a stale pre-suspend value behind
> for a subsequent ping timeout to report.
>
> Add lockdep_assert_held() in amd_sdw_read_ping_status() to document
> that the caller must hold msg_lock.
that lockdep_ add is a different improvement that should go in a
separate patch - it's not related to the timeout management and the
suggested use of a cached value.
> Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
> ---
> drivers/soundwire/amd_manager.c | 21 ++++++++++++++++++++-
> include/linux/soundwire/sdw_amd.h | 4 ++++
> 2 files changed, 24 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/soundwire/amd_manager.c b/drivers/soundwire/amd_manager.c
> index fa3f4e797edd..a57b59609bfe 100644
> --- a/drivers/soundwire/amd_manager.c
> +++ b/drivers/soundwire/amd_manager.c
> @@ -453,6 +453,9 @@ static void amd_sdw_read_and_process_ping_status(struct amd_sdw_manager *amd_man
> amd_manager->instance);
> return;
> }
> + amd_manager->ping_slave_stat =
> + FIELD_GET(AMD_SDW_MCP_SLAVE_STAT_0_3, response) |
> + (FIELD_GET(AMD_SDW_MCP_SLAVE_STAT_4_11, response) << 8);
> amd_sdw_process_ping_status(response, amd_manager);
> mutex_unlock(&amd_manager->bus.msg_lock);
> }
> @@ -463,15 +466,19 @@ static u32 amd_sdw_read_ping_status(struct sdw_bus *bus)
> u64 response;
> u32 slave_stat;
>
> + /* Called by sdw_show_ping_status() which holds msg_lock. */
> + lockdep_assert_held(&bus->msg_lock);
> +
> if (amd_sdw_send_cmd_get_resp(amd_manager, 0, 0, &response)) {
> dev_err_ratelimited(amd_manager->dev, "SDW%x ping status timeout\n",
> amd_manager->instance);
> - return 0;
> + return amd_manager->ping_slave_stat == U32_MAX ? 0 : amd_manager->ping_slave_stat;
> }
> /* slave status from ping response */
> slave_stat = FIELD_GET(AMD_SDW_MCP_SLAVE_STAT_0_3, response);
> slave_stat |= FIELD_GET(AMD_SDW_MCP_SLAVE_STAT_4_11, response) << 8;
> dev_dbg(amd_manager->dev, "slave_stat:0x%x\n", slave_stat);
> + amd_manager->ping_slave_stat = slave_stat;
> return slave_stat;
> }
>
> @@ -1087,6 +1094,7 @@ static int amd_sdw_manager_probe(struct platform_device *pdev)
> dev_err(dev, "mmio not found\n");
> return -ENOMEM;
> }
> + amd_manager->ping_slave_stat = U32_MAX;
> amd_manager->instance = pdata->instance;
> amd_manager->mmio = amd_manager->acp_mmio +
> (amd_manager->instance * SDW_MANAGER_REG_OFFSET);
> @@ -1414,6 +1422,17 @@ static int __maybe_unused amd_resume_runtime(struct device *dev)
> }
> } else if (amd_manager->power_mode_mask & AMD_SDW_POWER_OFF_MODE) {
> writel(0x00, amd_manager->acp_mmio + ACP_SW_WAKE_EN(amd_manager->instance));
> + /*
> + * POWER_OFF_MODE tears the bus down completely; invalidate the
> + * cached ping status on entry, before any step that can fail and
> + * return early, so that a partially-failed resume leaves the first
> + * post-resume ping timeout returning 0 rather than stale
> + * pre-suspend data. CLK_STOP_MODE leaves peripherals attached, so
> + * the cache remains valid there.
> + */
> + mutex_lock(&amd_manager->bus.msg_lock);
> + amd_manager->ping_slave_stat = U32_MAX;
> + mutex_unlock(&amd_manager->bus.msg_lock);
> if (amd_manager->acp_rev >= ACP70_PCI_REV_ID) {
> ret = amd_sdw_host_wake_enable(amd_manager, false);
> if (ret)
> diff --git a/include/linux/soundwire/sdw_amd.h b/include/linux/soundwire/sdw_amd.h
> index 470360a2723c..d0e97007e3ff 100644
> --- a/include/linux/soundwire/sdw_amd.h
> +++ b/include/linux/soundwire/sdw_amd.h
> @@ -76,6 +76,9 @@ struct sdw_amd_dai_runtime {
> * @acp_rev: acp pci device revision id
> * @clk_stopped: flag set to true when clock is stopped
> * @power_mode_mask: flag interprets amd SoundWire manager power mode
> + * @ping_slave_stat: cached slave status from the last ping
> + * transaction that returned a response;
> + * initialised to U32_MAX ("no valid reading yet")
> * @dai_runtime_array: dai runtime array
> */
> struct amd_sdw_manager {
> @@ -105,6 +108,7 @@ struct amd_sdw_manager {
> u32 wake_en_mask;
> u32 power_mode_mask;
> u32 acp_rev;
> + u32 ping_slave_stat;
> bool clk_stopped;
>
> struct sdw_amd_dai_runtime **dai_runtime_array;
next prev parent reply other threads:[~2026-10-18 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 8:49 [PATCH V3 00/10] soundwire: amd: SoundWire manager driver bug fixes Vijendar Mukunda
2026-10-13 8:49 ` [PATCH V3 01/10] soundwire: amd: fix SDW command timeout return value handling Vijendar Mukunda
2026-10-13 8:49 ` [PATCH V3 02/10] soundwire: amd: cache ping slave status to avoid spurious disconnect on timeout Vijendar Mukunda
2026-10-18 16:41 ` Pierre-Louis Bossart [this message]
2026-10-13 8:49 ` [PATCH V3 03/10] soundwire: amd: fix work drain ordering in remove path Vijendar Mukunda
2026-10-13 8:49 ` [PATCH V3 04/10] soundwire: amd: pm_runtime guard " Vijendar Mukunda
2026-10-13 8:49 ` [PATCH V3 05/10] soundwire: amd: fix ctx leak when sdw_amd_startup() fails Vijendar Mukunda
2026-10-13 8:49 ` [PATCH V3 06/10] soundwire: amd: propagate amd_init_sdw_manager() error on resume Vijendar Mukunda
2026-10-13 8:49 ` [PATCH V3 07/10] soundwire: amd: drop amd_deinit_sdw_manager() in POWER_OFF suspend Vijendar Mukunda
2026-10-13 8:49 ` [PATCH V3 08/10] soundwire: amd: replace >= ACP70 with explicit switch/case in PM paths Vijendar Mukunda
2026-10-13 8:49 ` [PATCH V3 09/10] soundwire: amd: fix interrupt gate and work drain ordering in PM ops Vijendar Mukunda
2026-10-13 8:49 ` [PATCH V3 10/10] soundwire: amd: fix IRQ thread dropping STATUS_0TO7 on simultaneous wake Vijendar Mukunda
2026-10-18 16:49 ` Pierre-Louis Bossart
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=94e1b390-903c-4a34-bd9e-9c128b6c1622@linux.dev \
--to=pierre-louis.bossart@linux.dev \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Richard.Gong@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Syed.SabaKareem@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=venkataprasad.potturu@amd.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
all inboxes | Powered by JetHome®