From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Ville Saarinen <wiza@saarinenkoti.fi>,
Shenghao Ding <shenghao-ding@ti.com>, Kevin Lu <kevin-lu@ti.com>,
Baojun Xu <baojun.xu@ti.com>, Sen Wang <sen@ti.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Charles Keepax <ckeepax@opensource.cirrus.com>
Subject: Re: [PATCH 1/3] ASoC: tas2783: let regmap-sdw-mbq poll for deferred transactions
Date: Sun, 9 Aug 2026 21:13:48 +0200 [thread overview]
Message-ID: <b2ae6045-6f8c-431f-978c-63158d3a4e9d@linux.dev> (raw)
In-Reply-To: <51a70023-9eaf-4d50-8b87-60fdb73cf08a@saarinenkoti.fi>
> Thanks for taking the time to review this. I am a bit of a kernel noob,
> but I completely agree with you and the spec: FUNCTION_STATUS cannot be
> deferred.
>
> I think my commit message caused a misunderstanding. The patch doesn't
> defer the status read:
>
> The hardware is actually returning COMMAND_IGNORED for the UDMPU23
> Cluster Index write, which is the only control tas2783_sdca_deferrable()
> flags as true.
>
> I only added FUNCTION_STATUS to mbq_size to expose it to ->
> readable_reg(). Without that, regmap_sdw_mbq_poll_busy() considers the
> status register unreadable, skips checking the busy bit for the deferred
> UDMPU23 write, and instantly fails.
I think your patch exposes a problem in the initial implementation of
regmap_sdw_mbq_poll_busy(). FUNCTION_STATUS is a readable register by
default, not sure why we would ever need to test if it's readable.
Adding Charles for additional comments, this part looks questionable
with a possible register side-effect.
reg = SDW_SDCA_CTL(SDW_SDCA_CTL_FUNC(reg), 0,
SDCA_CTL_ENTITY_0_FUNCTION_STATUS, 0);
if (ctx->readable_reg(dev, reg)) { <<< are we testing the correct reg?
next prev parent reply other threads:[~2026-08-09 19:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 10:15 [PATCH 0/3] ASoC: tas2783: fix stereo split and resume on a two-amp pair Ville Saarinen
2026-08-09 10:16 ` [PATCH 1/3] ASoC: tas2783: let regmap-sdw-mbq poll for deferred transactions Ville Saarinen
2026-08-09 14:05 ` Pierre-Louis Bossart
2026-08-09 17:41 ` Ville Saarinen
2026-08-09 19:13 ` Pierre-Louis Bossart [this message]
2026-08-11 12:19 ` Charles Keepax
2026-08-09 10:16 ` [PATCH 2/3] ASoC: tas2783: add RX Single Channel Switch to split a two-amp stereo pair Ville Saarinen
2026-08-09 10:16 ` [PATCH 3/3] ASoC: tas2783: drop firmware-owned registers from the regmap cache Ville Saarinen
2026-08-12 19:05 ` Mark Brown
2026-08-12 21:18 ` Ville Saarinen
2026-08-13 18:30 ` Andrey Golovko
2026-08-09 10:36 ` [PATCH 0/3] ASoC: tas2783: fix stereo split and resume on a two-amp pair Ville Saarinen
2026-08-11 12:48 ` Robin Everaars
2026-08-11 13:55 ` Ville Saarinen
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=b2ae6045-6f8c-431f-978c-63158d3a4e9d@linux.dev \
--to=pierre-louis.bossart@linux.dev \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--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®