All of lore.kernel.org
 help / color / mirror / Atom feed
From: jeffy <jeffy.chen@rock-chips.com>
To: Mark Brown <broonie@kernel.org>
Cc: Oder Chiou <oder_chiou@realtek.com>,
	alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
	heiko@sntech.de, Liam Girdwood <lgirdwood@gmail.com>,
	briannorris@chromium.org, dianders@chromium.org,
	linux-kernel@vger.kernel.org, mka@chromium.org,
	Takashi Iwai <tiwai@suse.com>, Bard Liao <bardliao@realtek.com>,
	dgreid@chromium.org
Subject: Re: [PATCH v4 1/9] ASoC: rt5514: Avoid legacy dai naming
Date: Tue, 22 Aug 2017 12:20:20 +0800	[thread overview]
Message-ID: <599BB104.4020600@rock-chips.com> (raw)
In-Reply-To: <20170821173107.wzkbnvqylkovg634@sirena.org.uk>

Hi Mark,

thanks for your reply.

On 08/22/2017 01:31 AM, Mark Brown wrote:
> On Fri, Aug 18, 2017 at 11:03:46PM +0800, jeffy wrote:
>
>> when using legacy dai naming, the dai->name for rt5514-spi would be the dev
>> name, which is spi2.0 with my local 4.4 kernel, and would be spi32765.0 with
>> upstream kernel.
>
> It would be better to fix the code to not need a name if the device by
> itself is unambiguous.
>

right...

i'm not familiar with the soc core codes, would these make sense?

1/ consider match when the of nodes are the same:

@@ -978,9 +978,10 @@ struct snd_soc_dai *snd_soc_find_dai(
                 if (dlc->name && strcmp(component->name, dlc->name))
                         continue;
                 list_for_each_entry(dai, &component->dai_list, list) {
+                       if (dlc->of_node && dai->dev->of_node == 
dlc->of_node)
+                               return dai;

or
2/ return the first dai when there's only one:

@@ -977,10 +977,11 @@ struct snd_soc_dai *snd_soc_find_dai(
                         continue;
                 if (dlc->name && strcmp(component->name, dlc->name))
                         continue;
+               if (component->num_dai == 1)
+                       return &component->dai_list[0];
                 list_for_each_entry(dai, &component->dai_list, list) {

or
3/ also check for dai driver name:

@@ -978,9 +978,10 @@ struct snd_soc_dai *snd_soc_find_dai(
                 if (dlc->name && strcmp(component->name, dlc->name))
                         continue;
                 list_for_each_entry(dai, &component->dai_list, list) {
-                       if (dlc->dai_name && strcmp(dai->name, 
dlc->dai_name))
+                       if (dlc->dai_name && strcmp(dai->name, 
dlc->dai_name)
+                           && strcmp(dai->driver->name, dlc->dai_name))
                                 continue;

WARNING: multiple messages have this Message-ID (diff)
From: jeffy <jeffy.chen@rock-chips.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, dgreid@chromium.org,
	heiko@sntech.de, briannorris@chromium.org, mka@chromium.org,
	dianders@chromium.org, Jaroslav Kysela <perex@perex.cz>,
	alsa-devel@alsa-project.org, Oder Chiou <oder_chiou@realtek.com>,
	Takashi Iwai <tiwai@suse.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Bard Liao <bardliao@realtek.com>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v4 1/9] ASoC: rt5514: Avoid legacy dai naming
Date: Tue, 22 Aug 2017 12:20:20 +0800	[thread overview]
Message-ID: <599BB104.4020600@rock-chips.com> (raw)
In-Reply-To: <20170821173107.wzkbnvqylkovg634@sirena.org.uk>

Hi Mark,

thanks for your reply.

On 08/22/2017 01:31 AM, Mark Brown wrote:
> On Fri, Aug 18, 2017 at 11:03:46PM +0800, jeffy wrote:
>
>> when using legacy dai naming, the dai->name for rt5514-spi would be the dev
>> name, which is spi2.0 with my local 4.4 kernel, and would be spi32765.0 with
>> upstream kernel.
>
> It would be better to fix the code to not need a name if the device by
> itself is unambiguous.
>

right...

i'm not familiar with the soc core codes, would these make sense?

1/ consider match when the of nodes are the same:

@@ -978,9 +978,10 @@ struct snd_soc_dai *snd_soc_find_dai(
                 if (dlc->name && strcmp(component->name, dlc->name))
                         continue;
                 list_for_each_entry(dai, &component->dai_list, list) {
+                       if (dlc->of_node && dai->dev->of_node == 
dlc->of_node)
+                               return dai;

or
2/ return the first dai when there's only one:

@@ -977,10 +977,11 @@ struct snd_soc_dai *snd_soc_find_dai(
                         continue;
                 if (dlc->name && strcmp(component->name, dlc->name))
                         continue;
+               if (component->num_dai == 1)
+                       return &component->dai_list[0];
                 list_for_each_entry(dai, &component->dai_list, list) {

or
3/ also check for dai driver name:

@@ -978,9 +978,10 @@ struct snd_soc_dai *snd_soc_find_dai(
                 if (dlc->name && strcmp(component->name, dlc->name))
                         continue;
                 list_for_each_entry(dai, &component->dai_list, list) {
-                       if (dlc->dai_name && strcmp(dai->name, 
dlc->dai_name))
+                       if (dlc->dai_name && strcmp(dai->name, 
dlc->dai_name)
+                           && strcmp(dai->driver->name, dlc->dai_name))
                                 continue;

  reply	other threads:[~2017-08-22  4:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18  3:11 [PATCH v4 0/9] ASoC: rockchip: Parse dai links from dts Jeffy Chen
2017-08-18  3:11 ` Jeffy Chen
2017-08-18  3:11 ` [PATCH v4 1/9] ASoC: rt5514: Avoid legacy dai naming Jeffy Chen
2017-08-18 11:45   ` Mark Brown
2017-08-18 15:03     ` jeffy
2017-08-21 17:31       ` Mark Brown
2017-08-22  4:20         ` jeffy [this message]
2017-08-22  4:20           ` jeffy
2017-08-18  3:11 ` [PATCH v4 2/9] ASoC: rockchip: Remove obsolete dmic-delay Jeffy Chen
2017-08-18  3:11   ` Jeffy Chen
2017-08-22  2:42   ` Rob Herring
2017-08-22  2:42     ` Rob Herring
2017-08-18  3:11 ` [PATCH v4 3/9] ASoC: rockchip: Use codec of_node and dai_name for rt5514 dsp Jeffy Chen
2017-08-18  3:11   ` Jeffy Chen
     [not found] ` <20170818031147.16810-1-jeffy.chen-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-08-18  3:11   ` [PATCH v4 4/9] arm64: dts: rockchip: Add rt5514 dsp for Gru Jeffy Chen
2017-08-18  3:11     ` Jeffy Chen
2017-08-18  3:11     ` Jeffy Chen
2017-08-18  3:11 ` [PATCH v4 5/9] arm64: dts: rockchip: Update rt5514 devices' compatible " Jeffy Chen
2017-08-18  3:11   ` Jeffy Chen
2017-08-18  3:11 ` [PATCH v4 6/9] ASoC: rockchip: Parse dai links from dts Jeffy Chen
2017-08-18  3:11   ` Jeffy Chen
2017-08-21 21:56   ` Matthias Kaehlcke
2017-08-21 21:56     ` Matthias Kaehlcke
2017-08-21 21:56     ` Matthias Kaehlcke
2017-08-18  3:11 ` [PATCH v4 7/9] ASoC: rockchip: Add support for DP codec Jeffy Chen
2017-08-18  3:11   ` Jeffy Chen
2017-08-18  3:11 ` [PATCH v4 8/9] ASoC: rockchip: Add support for DMIC codec Jeffy Chen
2017-08-18  3:11   ` Jeffy Chen
2017-08-18  3:11 ` [PATCH v4 9/9] dt-bindings: ASoC: rockchip: Update description of rockchip,codec Jeffy Chen
2017-08-18  3:11   ` [PATCH v4 9/9] dt-bindings: ASoC: rockchip: Update description of rockchip, codec Jeffy Chen

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=599BB104.4020600@rock-chips.com \
    --to=jeffy.chen@rock-chips.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bardliao@realtek.com \
    --cc=briannorris@chromium.org \
    --cc=broonie@kernel.org \
    --cc=dgreid@chromium.org \
    --cc=dianders@chromium.org \
    --cc=heiko@sntech.de \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=oder_chiou@realtek.com \
    --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.