From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
Cc: 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>,
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
Subject: Re: [PATCH 1/3] ASoC: tas2783: let regmap-sdw-mbq poll for deferred transactions
Date: Tue, 11 Aug 2026 13:19:08 +0100 [thread overview]
Message-ID: <ansTPGgVNoDJlA5r@opensource.cirrus.com> (raw)
In-Reply-To: <b2ae6045-6f8c-431f-978c-63158d3a4e9d@linux.dev>
On Sun, Aug 09, 2026 at 09:13:48PM +0200, Pierre-Louis Bossart wrote:
>
> > 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?
Yeah this is doing what is intended. I guess it is technically
not spec compliant to not have a readable Function Status but I
don't see the harm in supporting it here.
The patch here looks pretty good for the tas driver, it definitely
wants those timeouts and the function status should definitely be
added to the regmap. The bit about the timeouts being the wrong
way round is pretty concerning, will need to double check that but
will send a patch later today if that is true. Probably better
to patch the core and update this patch to use the corrected
core. I will look into that and get a patch out.
Thanks,
Charles
next prev parent reply other threads:[~2026-08-11 12:19 UTC|newest]
Thread overview: 11+ 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
2026-08-11 12:19 ` Charles Keepax [this message]
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-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=ansTPGgVNoDJlA5r@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--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=perex@perex.cz \
--cc=pierre-louis.bossart@linux.dev \
--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