From: Mark Brown <broonie@kernel.org>
To: Shengjiu Wang <shengjiu.wang@nxp.com>
Cc: timur@kernel.org, nicoleotsuka@gmail.com, Xiubo.Lee@gmail.com,
festevam@gmail.com, perex@perex.cz, tiwai@suse.com,
alsa-devel@alsa-project.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-5.15 0/5] ASoC: fsl: register platform component before registering cpu dai
Date: Mon, 6 Sep 2021 12:47:01 +0100 [thread overview]
Message-ID: <20210906114701.GC4309@sirena.org.uk> (raw)
In-Reply-To: <1630665006-31437-1-git-send-email-shengjiu.wang@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
On Fri, Sep 03, 2021 at 06:30:01PM +0800, Shengjiu Wang wrote:
> There is no defer probe when adding platform component to
> snd_soc_pcm_runtime(rtd), the code is in snd_soc_add_pcm_runtime()
...
> So if the platform component is not ready at that time, then the
> sound card still registered successfully, but platform component
> is empty, the sound card can't be used.
This sounds like a bug which should be fixed there?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-09-06 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 10:30 [PATCH for-5.15 0/5] ASoC: fsl: register platform component before registering cpu dai Shengjiu Wang
2021-09-03 10:30 ` [PATCH for-5.15 1/5] ASoC: fsl_sai: " Shengjiu Wang
2021-09-03 10:30 ` [PATCH for-5.15 2/5] ASoC: fsl_esai: " Shengjiu Wang
2021-09-03 10:30 ` [PATCH for-5.15 3/5] ASoC: fsl_micfil: " Shengjiu Wang
2021-09-03 10:30 ` [PATCH for-5.15 4/5] ASoC: fsl_spdif: " Shengjiu Wang
2021-09-03 10:30 ` [PATCH for-5.15 5/5] ASoC: fsl_xcvr: " Shengjiu Wang
2021-09-06 11:47 ` Mark Brown [this message]
2021-09-07 2:43 ` [PATCH for-5.15 0/5] ASoC: fsl: " Shengjiu Wang
2021-09-10 10:16 ` Mark Brown
2021-09-10 16:08 ` 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=20210906114701.GC4309@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=shengjiu.wang@nxp.com \
--cc=timur@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).