From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Daniel Baluta <daniel.baluta@gmail.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] Counting links in simple-card
Date: 11 Oct 2019 09:41:01 +0900 [thread overview]
Message-ID: <87v9sww1uq.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <CAEnQRZDZc3vWVQTTa37opRs7aqx8xzTHTBB3oHXCrmeFTZRBhQ@mail.gmail.com>
Hi Daniel
Thank you for your email
> I think I can modify simple-card to do this. Just let me know if you
> see something obviously wrong
> on making the simple-card / simple-scu-card handling this case with
> creating just 1 BE DAI link.
Current DPCM support is used for "TDM-Split mode",
"MIXer", "Sampling rate convert" for now.
But, of course I have no objection if you can add new feature.
> simple-audio-card,dai-link@2 {
> cpu {
> sound-dai=<&cpu1>;
> }
> }
It looks FE, but is this for BE ?
> Maybe add a property like "dpcm".
I think property "dpcm" is very ALSA-SoC naming, DT guy don't like it (?).
"simple-xxx-card" (1) or new node (2) can be acceptable ?
I'm not sure...
machine_drv {
(1) compatible = "simple-xxx-card";
...
simple-audio-card,dai-link@2 {
(2) dpcm-fe {
sound-dai=<&cpu1>;
...
Thank you for your help !!
Best regards
---
Kuninori Morimoto
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2019-10-11 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 13:03 [alsa-devel] Counting links in simple-card Daniel Baluta
2019-10-08 13:30 ` Daniel Baluta
2019-10-09 0:18 ` Kuninori Morimoto
2019-10-09 8:31 ` Daniel Baluta
2019-10-09 23:37 ` Kuninori Morimoto
2019-10-10 14:46 ` Daniel Baluta
2019-10-10 20:40 ` Daniel Baluta
2019-10-11 0:41 ` Kuninori Morimoto [this message]
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=87v9sww1uq.wl-kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.baluta@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;
as well as URLs for NNTP newsgroup(s).