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: Thu, 21 Dec 2017 11:25:44 +0000 [thread overview]
Message-ID: <20171221112544.GE6754@sirena.org.uk> (raw)
In-Reply-To: <87o9msc1zk.wl%kuninori.morimoto.gx@renesas.com>
[-- Attachment #1.1: Type: text/plain, Size: 1235 bytes --]
On Thu, Dec 21, 2017 at 01:28:09AM +0000, Kuninori Morimoto wrote:
> If my understanding was correct, we can call all DAIs
> by one for_each loop with controllable order on your idea.
> This is nice.
> But, callback order will be exchanged ?
> For example soc_pcm_trigger() case, .trigger callback order currently is
> Codec DAI -> Component(Platform) -> CPU DAI -> RTD
> it will be
> all ordered DAIs -> Component(Platform) -> RTD
> Codec / CPU callback order are OK, but DAI / Component order is exchanged.
> If this is not a big problem, we can do it.
Ah, yes - we'd need to mix in the platform :/
> And one issue I noticed.
> If we merged all Codec/CPU DAI into one DAI list, and without
> flags (like .peripheral flag), current DAI master/slave direction will be problem.
Yes, there's other things need to be fixed - I'm not saying it'd be a
simple transition.
> At least snd_soc_runtime_set_dai_fmt() is switching it for Codec <-> Codec case.
> If we can change current SND_SOC_DAIFMT_CBx_CFx style to
> xx_MASTER / xx_SLAVE style on each DAIs, this can be no problem I think.
> I guess Lars is thinking about it ?
It's been talked about for years but it's another of these things that's
a lot of work to transition.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2017-12-21 11:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171208084103.GC18649@localhost>
[not found] ` <87fu8lio74.wl%kuninori.morimoto.gx@renesas.com>
[not found] ` <20171208105545.GE18649@localhost>
[not found] ` <87shciup8e.wl%kuninori.morimoto.gx@renesas.com>
[not found] ` <87r2s2uo55.wl%kuninori.morimoto.gx@renesas.com>
[not found] ` <87o9n6ukyg.wl%kuninori.morimoto.gx@renesas.com>
2017-12-13 7:19 ` About ASoC DAIs cleanup Kuninori Morimoto
2017-12-13 15:59 ` Mark Brown
2017-12-14 3:07 ` Kuninori Morimoto
2017-12-14 5:06 ` Vinod Koul
2017-12-14 5:24 ` Kuninori Morimoto
2017-12-14 11:37 ` Mark Brown
2017-12-15 4:20 ` Vinod Koul
2017-12-18 2:16 ` Kuninori Morimoto
2017-12-19 11:23 ` Mark Brown
2017-12-21 1:28 ` Kuninori Morimoto
2017-12-21 11:25 ` Mark Brown [this message]
2017-12-22 1:23 ` 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=20171221112544.GE6754@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lars@metafoo.de \
--cc=shreyas.nc@intel.com \
--cc=vinod.koul@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox