[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEnQRZDe_Q-N7L_7z7aVz1o3guKd6R+WFrOfT9KPbggJP8SPZw@mail.gmail.com>
Date: Fri, 12 Mar 2021 12:59:29 +0200
From: Daniel Baluta <daniel.baluta@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Daniel Baluta <daniel.baluta@....nxp.com>,
Linux-ALSA <alsa-devel@...a-project.org>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
dl-linux-imx <linux-imx@....com>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
"S.j. Wang" <shengjiu.wang@....com>,
Daniel Baluta <daniel.baluta@....com>
Subject: Re: [PATCH] ASoC: core: Don't set platform name when of_node is set
On Fri, Mar 12, 2021 at 12:50 PM Mark Brown <broonie@...nel.org> wrote:
>
> On Fri, Mar 12, 2021 at 10:32:54AM +0200, Daniel Baluta wrote:
> > On Tue, Mar 9, 2021 at 5:38 PM Mark Brown <broonie@...nel.org> wrote:
>
> > > > + if (!dai_link->platforms->of_node)
> > > > + dai_link->platforms->name = component->name;
>
> > > Why would we prefer the node name over something explicitly configured?
>
> > Not sure I follow your question. I think the difference stands in the
> > way we treat OF vs non-OF platforms.
>
> If an explicit name has been provided why would we override it with an
> autogenerated one?
Wait, are you asking why the initial code:
dai_link->platforms->name = component->name;
is there in the initial code?
Powered by blists - more mailing lists