From: Mark Brown <broonie@kernel.org>
To: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Cc: Kate Stewart <kstewart@linuxfoundation.org>,
Cezary Rojewski <cezary.rojewski@intel.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Jie Yang <yang.jie@linux.intel.com>,
alsa-devel@alsa-project.org,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Richard Fontana <rfontana@redhat.com>,
Shunli Wang <shunli.wang@mediatek.com>,
YueHaibing <yuehaibing@huawei.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Jiaxin Yu <jiaxin.yu@mediatek.com>,
linux-arm-kernel@lists.infradead.org,
Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
Stephen Boyd <swboyd@chromium.org>,
linux-mediatek@lists.infradead.org,
Eason Yen <eason.yen@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Allison Randal <allison@lohutok.net>,
Takashi Iwai <tiwai@suse.com>,
Ravulapati Vishnu vardhan rao
<Vishnuvardhanrao.Ravulapati@amd.com>,
Colin Ian King <colin.king@canonical.com>
Subject: Re: [PATCH 0/4] ASoC:: don't use snd_soc_rtdcom_lookup()
Date: Thu, 23 Apr 2020 11:53:17 +0100 [thread overview]
Message-ID: <20200423105317.GE4808@sirena.org.uk> (raw)
In-Reply-To: <ebe305743178c4548b779f25e6400863094ef5a9.camel@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
On Wed, Apr 22, 2020 at 03:39:58PM -0700, Ranjani Sridharan wrote:
> On Thu, 2020-04-23 at 07:12 +0900, Kuninori Morimoto wrote:
> > I'm thinking removing lookup function is nice idea,
> > but don't feel pressure to it.
> > "Now you know it" is very enough for me.
> I am having a hard time visualizing a scenario where we would have more
> than one platform component. And even if we did, I'd think that the
> driver registering these components would make sure to not duplicate
> the driver names. Of course, we dont really check if thats really the
> case.
The only use case I can think of is a link where there's a CPU on both
ends for some reason.
> Do you think it makes sense to add that check when registering a
> component? If we do that, then keeping snd_soc_rtdcom_lookup() might
> not be such a bad idea.
Yeah.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-04-23 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 4:46 [PATCH 0/4] ASoC:: don't use snd_soc_rtdcom_lookup() Kuninori Morimoto
2020-04-22 4:48 ` [PATCH 1/4] ASoC: mediatek: " Kuninori Morimoto
2020-04-22 4:48 ` [PATCH 2/4] ASoC: intel: baytrail: " Kuninori Morimoto
2020-04-22 4:48 ` [PATCH 3/4] ASoC: intel: haswell: " Kuninori Morimoto
2020-04-22 4:48 ` [PATCH 4/4] ASoC: amd: " Kuninori Morimoto
2020-04-22 5:39 ` [PATCH 0/4] ASoC:: " Ranjani Sridharan
2020-04-22 22:12 ` Kuninori Morimoto
2020-04-22 22:39 ` Ranjani Sridharan
2020-04-22 23:56 ` Kuninori Morimoto
2020-04-23 10:53 ` Mark Brown [this message]
2020-04-23 15:31 ` Ranjani Sridharan
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=20200423105317.GE4808@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Vijendar.Mukunda@amd.com \
--cc=Vishnuvardhanrao.Ravulapati@amd.com \
--cc=allison@lohutok.net \
--cc=alsa-devel@alsa-project.org \
--cc=cezary.rojewski@intel.com \
--cc=colin.king@canonical.com \
--cc=eason.yen@mediatek.com \
--cc=jiaxin.yu@mediatek.com \
--cc=kstewart@linuxfoundation.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=rfontana@redhat.com \
--cc=shunli.wang@mediatek.com \
--cc=swboyd@chromium.org \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.com \
--cc=yang.jie@linux.intel.com \
--cc=yuehaibing@huawei.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