Re: About ASoC DAIs cleanup

From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
	Linux-ALSA <alsa-devel@alsa-project.org>,
	Lars-Peter <lars@metafoo.de>, Shreyas NC <shreyas.nc@intel.com>
Subject: Re: About ASoC DAIs cleanup
Date: Tue, 19 Dec 2017 11:23:02 +0000	[thread overview]
Message-ID: <20171219112302.GI8563@sirena.org.uk> (raw)
In-Reply-To: <87mv2grdqm.wl%kuninori.morimoto.gx@renesas.com>


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

On Mon, Dec 18, 2017 at 02:16:07AM +0000, Kuninori Morimoto wrote:

> My quick idea is using "peripheral" flag.
> I think we can set it on soc_bind_dai_link() ?
> And we can use it like below

> 	for_each_dais(dai, xxx) {
> 		if(!dai->peripheral)
> 			/* non Peripheral == CPU portion */
> 
> 		if(dai->peripheral)
> 			/* Peripheral == Codec portion */
> 	}

> But what do you think about this idea/naming etc ?
> I want to investigate more about Codec <-> Codec connection,
> which driver is using it ? Especially CPU portion

I'm thinking it might be better to keep the list ordered in the DAI link
- that will scale up better with multi-drop links.  What's going to be a
bit more tricky sometimes is working out which end of the link is a CPU
DAI but we can probably take a good guess easily enough on order neutral
bindings and things liken simple-card already know explicitly.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

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