From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
Cezary Rojewski <cezary.rojewski@intel.com>
Cc: tiwai@suse.com, perex@perex.cz, amade@asmblr.net,
kuninori.morimoto.gx@renesas.com, linux-sound@vger.kernel.org,
"Liao, Bard" <bard.liao@intel.com>,
"Vehmanen, Kai" <kai.vehmanen@intel.com>,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>
Subject: Re: [PATCH] ASoC: core: Move all users to deferrable card binding
Date: Mon, 25 May 2026 15:48:36 +0300 [thread overview]
Message-ID: <b5e82c43-9da1-4a12-af0e-90d4b9feef49@linux.intel.com> (raw)
In-Reply-To: <85045e51-e09b-44c2-9266-3e7ee72c4eb0@sirena.org.uk>
On 22/05/2026 17:58, Mark Brown wrote:
> On Fri, May 22, 2026 at 04:32:03PM +0200, Cezary Rojewski wrote:
>
>> The question on the table: Do we revert the change temporarily, fix the SOF
>> first and then re-apply the patch again?
>
> Given that there's two drivers we managed to turn up bugs in already I'm
> inclined to leave the patch there so it's more likely that any other
> issues get found. It's a bit annoying for SOF CI but I guess a revert
> can be merged locally there?
It is not really the SOF CI but the users. it looks like all codecs
using SDCA infra is affected and will fail to probe audio on boot.
I did not has time to fully debug it, but how the currect system works
is that we don't and cannot know the DAI name of an SDCA function, they
are parsed and created by parsing the DiSCO table and they will have
FUNCTION_NAME.index, then index is a running number.
If the table has different ordering than for example UAJ can be
UAJ.1/2/3/etc.
The current way is to wait for the codecs (SDCA stack) to probe and
create the DAIs then we check and adjust the dai_link in the sof_sdw
machine driver.
If the SDCA function probes after the machine driver then we will never
have match for the dai link.
At the moment I don't see a reasonably quick workaround for this, but I
let Bard and Charles to comment.
Users of PTL are likely to be affected as their design seams to be
closely identical with most of them having cs42l45 codec for Jack, which
is SDCA only.
--
Péter
next prev parent reply other threads:[~2026-05-25 12:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 14:07 [PATCH] ASoC: core: Move all users to deferrable card binding Cezary Rojewski
2026-05-11 1:06 ` Mark Brown
2026-05-11 1:34 ` Kuninori Morimoto
2026-05-12 8:14 ` Rojewski, Cezary
2026-05-20 9:55 ` Alexander Stein
2026-05-20 10:33 ` Cezary Rojewski
2026-05-21 6:42 ` Alexander Stein
2026-05-21 8:13 ` Cezary Rojewski
2026-05-21 10:11 ` Alexander Stein
2026-05-21 14:41 ` Cezary Rojewski
2026-05-21 14:47 ` Alexander Stein
2026-05-22 11:21 ` Alexander Stein
2026-05-22 10:16 ` Péter Ujfalusi
2026-05-22 14:32 ` Cezary Rojewski
2026-05-22 14:58 ` Mark Brown
2026-05-22 15:08 ` Cezary Rojewski
2026-05-25 12:48 ` Péter Ujfalusi [this message]
2026-05-25 15:06 ` Mark Brown
2026-05-26 5:45 ` Péter Ujfalusi
2026-05-26 11:21 ` Péter Ujfalusi
2026-05-26 11:28 ` Péter Ujfalusi
2026-05-26 16:02 ` Mark Brown
2026-05-27 5:22 ` Péter Ujfalusi
2026-05-27 10:35 ` Mark Brown
2026-05-25 10:44 ` Pierre-Louis Bossart
2026-05-25 21:10 ` Cezary Rojewski
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=b5e82c43-9da1-4a12-af0e-90d4b9feef49@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=amade@asmblr.net \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=kai.vehmanen@intel.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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