Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	Simon <horms@verge.net.au>, Liam Girdwood <lgirdwood@gmail.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [PATCH] ASoC: simple-card: cpu_dai_name creates confusion when DT case
Date: Thu, 27 Feb 2014 14:07:26 +0900	[thread overview]
Message-ID: <20140227050726.GR9383@sirena.org.uk> (raw)
In-Reply-To: <87eh2r9169.wl%kuninori.morimoto.gx@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 594 bytes --]

On Mon, Feb 24, 2014 at 10:06:09PM -0800, Kuninori Morimoto wrote:
> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> 
> Basically, soc_bind_dai_link() checks
> cpu_dai->dev->of_node and dai_link->cpu_of_node in DT case.
> But after that it will check
> cpu_dai->name and dai_link->cpu_dai_name too.
> 
> On the other hand, snd_soc_dai :: name is created by
> fmt_single_name() or fmt_multiple_name().

This looks like a valid issue which still affects current code but it
doesn't apply due changes on the latest topic/simple branch.  Can you
please check and resend?

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2014-02-27  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25  6:06 [PATCH] ASoC: simple-card: cpu_dai_name creates confusion when DT case Kuninori Morimoto
2014-02-27  5:07 ` Mark Brown [this message]
2014-02-27 10:21   ` Kuninori Morimoto
2014-02-28  2:25     ` [PATCH v2] " Kuninori Morimoto
2014-02-28  3:53       ` Mark Brown
2014-02-28  4:31         ` Kuninori Morimoto
2014-02-28  5:25           ` 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=20140227050726.GR9383@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@gmail.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.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