From: Andrey Golovko <andrey.golovko@gmail.com>
To: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>,
Antoine Monnet <antoine@montane.tech>,
linux-sound@vger.kernel.org
Cc: shenghao-ding@ti.com, kevin-lu@ti.com, baojun.xu@ti.com,
broonie@kernel.org, lgirdwood@gmail.com, vkoul@kernel.org,
yung-chuan.liao@linux.intel.com, pierre-louis.bossart@linux.dev,
Mario Limonciello <superm1@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: ASoC: tas2783-sdw: calibration firmware not re-downloaded after s2idle resume (AMD ACP SoundWire, ASUS ProArt PX13)
Date: Mon, 27 Jul 2026 12:55:47 +0300 [thread overview]
Message-ID: <95b17762fa061f0195050f52dd02b946@gmail.com> (raw)
In-Reply-To: <13a5a03d-8263-443b-a6ba-84d954549b2b@amd.com>
> Could you please create Bugzilla ticket and attach dmesg logs?
Filed as https://bugzilla.kernel.org/show_bug.cgi?id=221798 and added you
to the CC list.
Attached there: the full kernel log of the boot containing the cycle, the
ACP register dumps from the silent and the working state plus their diff
(72 of 78 registers identical), the SoundWire peripheral register dumps
from both states plus their diff (the only difference being DP1
DPn_PrepareStatus 0x3 vs 0x0 on both amplifiers), and the DMA position
counter trace showing the ACP feeding the FIFO at the nominal 192000 B/s
while the speakers are silent.
Also cross-referenced there: bug 221584, which is the earlier
"peripherals stay unattached after s0i3" report on the same machine. That
one is fixed by your 5893013efabb in v7.2-rc4; it has not been picked up
for 7.1.y, where at least two more users are still hitting it.
Sorry about the duplicate copy of my previous mail - a command run twice.
Thanks,
Andrey
next prev parent reply other threads:[~2026-07-27 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 0:22 ASoC: tas2783-sdw: calibration firmware not re-downloaded after s2idle resume (AMD ACP SoundWire, ASUS ProArt PX13) Antoine Monnet
2026-07-27 8:13 ` Andrey Golovko
2026-07-27 9:04 ` Mukunda,Vijendar
2026-07-27 9:32 ` Andrey Golovko
2026-07-27 9:32 ` Andrey Golovko
2026-07-27 9:55 ` Andrey Golovko [this message]
2026-07-27 13:44 ` 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=95b17762fa061f0195050f52dd02b946@gmail.com \
--to=andrey.golovko@gmail.com \
--cc=antoine@montane.tech \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.dev \
--cc=shenghao-ding@ti.com \
--cc=superm1@kernel.org \
--cc=vijendar.mukunda@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.