From: Mark Brown <broonie@kernel.org>
To: Shengjiu Wang <shengjiu.wang@gmail.com>
Cc: Shengjiu Wang <shengjiu.wang@nxp.com>,
alsa-devel@alsa-project.org, Timur Tabi <timur@kernel.org>,
Xiubo Li <Xiubo.Lee@gmail.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Takashi Iwai <tiwai@suse.com>,
Nicolin Chen <nicoleotsuka@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH for-5.15 0/5] ASoC: fsl: register platform component before registering cpu dai
Date: Fri, 10 Sep 2021 11:16:01 +0100 [thread overview]
Message-ID: <20210910101601.GB4474@sirena.org.uk> (raw)
In-Reply-To: <CAA+D8APjyq74FECmH6ZzyVKHOz6MEV0bt+D4-Xkfc-6C5n9hZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
On Tue, Sep 07, 2021 at 10:43:26AM +0800, Shengjiu Wang wrote:
> It is hard to add conditions here for defer probe. And maybe
> some drivers need the same components for cpu and platform.
> Do you have any suggestions?
I would expect that in this situation the same component would be able
to fill both roles.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Shengjiu Wang <shengjiu.wang@gmail.com>
Cc: alsa-devel@alsa-project.org, Timur Tabi <timur@kernel.org>,
Xiubo Li <Xiubo.Lee@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Shengjiu Wang <shengjiu.wang@nxp.com>,
Takashi Iwai <tiwai@suse.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Nicolin Chen <nicoleotsuka@gmail.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH for-5.15 0/5] ASoC: fsl: register platform component before registering cpu dai
Date: Fri, 10 Sep 2021 11:16:01 +0100 [thread overview]
Message-ID: <20210910101601.GB4474@sirena.org.uk> (raw)
In-Reply-To: <CAA+D8APjyq74FECmH6ZzyVKHOz6MEV0bt+D4-Xkfc-6C5n9hZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
On Tue, Sep 07, 2021 at 10:43:26AM +0800, Shengjiu Wang wrote:
> It is hard to add conditions here for defer probe. And maybe
> some drivers need the same components for cpu and platform.
> Do you have any suggestions?
I would expect that in this situation the same component would be able
to fill both roles.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-09-10 10:16 UTC|newest]
Thread overview: 15+ 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 ` [PATCH for-5.15 0/5] ASoC: fsl: " Mark Brown
2021-09-06 11:47 ` Mark Brown
2021-09-06 11:47 ` Mark Brown
2021-09-07 2:43 ` Shengjiu Wang
2021-09-07 2:43 ` Shengjiu Wang
2021-09-10 10:16 ` Mark Brown [this message]
2021-09-10 10:16 ` Mark Brown
2021-09-10 16:08 ` 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=20210910101601.GB4474@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=shengjiu.wang@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.