All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Mark Brown <broonie@kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: 'modern dailink' transition
Date: 25 Mar 2019 12:19:52 +0900	[thread overview]
Message-ID: <878sx3ire2.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <87ftrbivbr.wl-kuninori.morimoto.gx@renesas.com>


Oops ??
I exchanged mail address

	- alsa-devel@alsa-devel.org
	+ alsa-devel@alsa-project.org

> Hi Pierre, Mark
> 
> > > I am however struggling with the notion of a 'snd-soc-dummy' platform that
> > > exists in some legacy Intel machine drivers. I changed the code following
> > > the pattern below but I have really no idea if this is correct. Shouldn't
> > > all dailinks either point to a real platform driver or not provide any
> > > information about the platform at all? Is there any specific expectation on
> > > the ASoC side here?
> 
> I guess my posted "no Platform" and "no implicit snd-soc-dummy" patch idea
> confused you. If so, I'm so sorry about that.
> I'm not sure this idea is Good or Bad.
> 
> > I'd expect the dummy driver to just get automatically substituted when
> > required, I'd not expect users to explicitly list it.
> 
> Yes agree.
> 
> This is my understanding, please correct me if I was wrong.
> I think current many sound card which doesn't need "platfrom" are 2 patterns.
> 
> 	1) select snd-soc-dummy as platfrom
> 	2) select cpu component as platfrom
> 
> Current ASoC selects 1) automatically if .platfrom_name was NULL.
> And driver needs to have below if it want to be 2)
> 
> 	dai_link->platform_of_node = dai_link->cpu_of_node
> 
> But, I think one of them is enough ?
> I mean select 2) automatically can be OK?
> In other words, current some sound card which doesn't need
> platfrom is calling snd-soc-dummy platfrom method in 1) case.
> But, is it needed ? I'm not sure...
> 
> It seems snd-soc-dummy platfrom is caring about DPCM-BE case,
> but, I think CPU is snd-soc-dummy in such case.
> Maybe we need same cade to dummy CPU (?), but *my* DPCM system
> is working correctly without it.
> 
> Best regards
> ---
> Kuninori Morimoto

       reply	other threads:[~2019-03-25  3:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <21d1e439-7ecd-dd6a-9a43-e66e8db1ac85@linux.intel.com>
     [not found] ` <20190321141242.GE5684@sirena.org.uk>
     [not found]   ` <87ftrbivbr.wl-kuninori.morimoto.gx@renesas.com>
2019-03-25  3:19     ` Kuninori Morimoto [this message]
2019-03-26  1:20       ` 'modern dailink' transition Kuninori Morimoto
2019-03-26 14:20     ` Mark Brown
2019-03-27 23:47       ` Kuninori Morimoto
2019-04-05  0:31         ` Kuninori Morimoto
2019-04-05 12:53           ` Pierre-Louis Bossart
2019-04-08  1:08             ` Kuninori Morimoto

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=878sx3ire2.wl-kuninori.morimoto.gx@renesas.com \
    --to=kuninori.morimoto.gx@renesas.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=pierre-louis.bossart@linux.intel.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.