From: Andrey Golovko <andrey.golovko@gmail.com>
To: Robin Everaars <robineveraars@pm.me>, Mark Brown <broonie@kernel.org>
Cc: Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
Shenghao Ding <shenghao-ding@ti.com>, Kevin Lu <kevin-lu@ti.com>,
Baojun Xu <baojun.xu@ti.com>, Sen Wang <sen@ti.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
"Holalu Yogendra, Niranjan" <niranjan.hy@ti.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
"Dommati, Sunil-kumar" <Sunil-kumar.Dommati@amd.com>,
Antoine Monnet <antoine@montane.tech>,
Ville Saarinen <wiza@saarinenkoti.fi>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: tas2783-sdw: power the Function up before preparing the port
Date: Fri, 14 Aug 2026 09:50:00 +0300 [thread overview]
Message-ID: <20260814095000.22512-1-andrey.golovko@gmail.com> (raw)
In-Reply-To: <20260813211858.17509-1-robineveraars@pm.me>
On Wed, Aug 13, 2026 at 09:18:58PM +0000, Robin Everaars wrote:
> thanks. One clarification about my negative v1 result: it was not an
> active-playback resume test. The controlled pre-suspend tone had completed
> before system suspend.
Thank you for going back and checking, that is a useful correction. I
had been reading your result as evidence about the resume ioctl, and it
is not.
Your second case is the one I would expect to have worked on v1: a fresh
pw-play after the sink was suspended opens the PCM again, so it goes
through hw_params() and prepare(), and that is the path v1 already
covered. It failing on v7.1.7 fits your own attribution to the missing
b627da430357 - without it the DAPM writes that follow are dropped
against a stale cache, so the Function never comes up no matter how well
the port is prepared. So yes, for-next rather than another v7.1.7 cycle.
For the third case I would expect it to still fail, and that is the
point of running it: the PCM core does not trigger a stream that was
left PREPARED, so nothing in the codec or machine driver gets a chance
to act. sdw_prepare_stream() on a stream still marked PREPARED is a
no-op too, so even a call from there would not help. It needs the
stream state invalidated when the peripheral goes UNATTACHED and comes
back. If your readout shows PrepareCtrl=0x0 while the stream is
running, that is the same gap and not a second bug.
The module is on its way off-list. It reads and prints DP1
PrepareCtrl, PrepareStatus, the ChannelEn of the current bank and the
PDE23 requested and actual power states, straight over the bus with
sdw_read_no_pm(), so the codec regmap cache is out of the picture. It
only reads unless you ask it to write.
For a shape to compare against, here is what the resume-ioctl case gave
on this machine, unpatched kernel to the left, v2 to the right:
DP1 PrepareCtrl before/after 0x1,0x2 -> 0x0,0x0 0x1,0x2 -> 0x1,0x2
PDE23 req/act after 0x3/0x3 0x0/0x0
440/660 Hz tone after -1.7/+1.8 dB +73.7/+88.5 dB
The tone figures are levels in narrow bands around 440 and 660 Hz in a
three-second capture from the built-in microphone, on a scale where a
capture of silence reads about 0 dB in the same bands. The absolute
numbers say nothing outside this machine; noise floor against signal
does.
v2 of the series is at
https://lore.kernel.org/linux-sound/20260813194000.10412-1-andrey.golovko@gmail.com/
Andrey
next prev parent reply other threads:[~2026-08-14 7:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 21:28 Andrey Golovko
2026-08-13 13:22 ` Mark Brown
2026-08-13 16:00 ` Mukunda,Vijendar
2026-08-13 16:45 ` Andrey Golovko
2026-08-13 21:19 ` Robin Everaars
2026-08-14 6:50 ` Andrey Golovko [this message]
2026-08-13 15:22 ` Robin Everaars
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=20260814095000.22512-1-andrey.golovko@gmail.com \
--to=andrey.golovko@gmail.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Vijendar.Mukunda@amd.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=niranjan.hy@ti.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.dev \
--cc=robineveraars@pm.me \
--cc=sen@ti.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.com \
--cc=wiza@saarinenkoti.fi \
/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®