From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Question about cpu_dai/codec_dai unbalance
Date: Tue, 27 Mar 2018 02:19:14 +0000 [thread overview]
Message-ID: <87y3ieb6v3.wl%kuninori.morimoto.gx@renesas.com> (raw)
Hi Mark, ALSA ML
Now, I'm investigating cpu_dai/codec_dai, and I noticed
there are many unbalance.
For example, snd_soc_suspend(),
it calls .digital_mute() only for codec_dai, not for cpc_dai,
and, calls .suspend() only for cpu_dai, not for codec_dai.
It seems there are many unbalance like this on ALSA SoC.
I know it is case-by-case, but I think we can have more balance.
For example above snd_soc_suspend() case, .digital_mute() is very common
for both cpu/codec I think, and, codec can have .suspend() ?
But what do you think ?
I think it doesn't breaks current system, because each cpu_dai doesn't
have .digital_mute(), and codec_dai doesn't have .suspend() for now.
Thus, nothing happen if I added it.
The reason why I'm asking is that
now, I'm thinking to merge cpu_dai/codec_dai into one dai list somehow.
This means, we can have non-categorized DAI, this is same as previous
codec/platform replacement into component.
Then, this kind of DAI unbalance might be problem.
Best regards
---
Kuninori Morimoto
reply other threads:[~2018-03-27 2:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87y3ieb6v3.wl%kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
/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;
as well as URLs for NNTP newsgroup(s).