From: Daniel Baluta <daniel.baluta@gmail.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Sameer Pujar <spujar@nvidia.com>, Mark Brown <broonie@kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: More Generic Audio Graph Sound Card idea
Date: Fri, 21 Aug 2020 10:11:29 +0300 [thread overview]
Message-ID: <CAEnQRZCsy+QiMpCCRPNF-BUcjaT+UVE2B_a6Bd48f8tRqXTpOA@mail.gmail.com> (raw)
In-Reply-To: <87k0xszlep.wl-kuninori.morimoto.gx@renesas.com>
On Fri, Aug 21, 2020 at 7:16 AM Kuninori Morimoto
<kuninori.morimoto.gx@renesas.com> wrote:
>
>
> Hi Mark
> Cc Pierre-Louis, Sameer
>
> Current audio-graph-card driver has DPCM support,
> but it is limited (= Mix/Mux/TDM-split/rate-convert/channel-convert).
> It was expanded forcibly expanded.
>
> Because of it, the connection judgement for normal vs DPCM is tricky.
> I know Pierre-Louis want to use it for SOF, but something is missing,
> thus, can't use (?).
Hi Morimoto-san,
Thanks for having a look at this. I also tried to use generic machine
driver (simple-card)
with SOF but I had some trouble creating desired DPCM links.
Main limitation of simple-card is that there is no direct way of
specifying DPCM links.
I had an attempt to introduce a more flexible approach for that here:
https://lkml.org/lkml/2019/10/13/123
but obviously we can do better than that.
For now, I'm using only normal links with simple-audio card and it
works fine for
me with SOF, but in the future I think we might need to expand that.
next prev parent reply other threads:[~2020-08-21 7:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 4:15 More Generic Audio Graph Sound Card idea Kuninori Morimoto
2020-08-21 5:26 ` Sameer Pujar
2020-08-21 7:14 ` Kuninori Morimoto
2020-08-21 8:28 ` Sameer Pujar
2020-08-21 13:02 ` Mark Brown
2020-09-25 1:43 ` Kuninori Morimoto
2020-09-25 19:22 ` Mark Brown
2020-09-25 20:04 ` Pierre-Louis Bossart
2020-09-25 20:10 ` Mark Brown
2020-09-25 20:50 ` Pierre-Louis Bossart
2020-08-21 7:11 ` Daniel Baluta [this message]
2020-08-21 7:25 ` Kuninori Morimoto
2020-08-21 7:33 ` Daniel Baluta
2020-08-21 11:47 ` Mark Brown
2020-08-21 12:18 ` Mark Brown
2020-08-24 0:25 ` Kuninori Morimoto
2020-08-24 6:25 ` Sameer Pujar
2020-08-25 0:59 ` Kuninori Morimoto
2020-08-25 3:11 ` Sameer Pujar
2020-08-25 5:13 ` Kuninori Morimoto
2020-08-25 5:42 ` Sameer Pujar
2020-08-25 6:35 ` Kuninori Morimoto
2020-08-26 6:46 ` Sameer Pujar
2020-08-27 1:18 ` Kuninori Morimoto
2020-08-27 1:36 ` Kuninori Morimoto
2020-09-03 23:51 ` Kuninori Morimoto
2020-09-09 11:33 ` Sameer Pujar
2020-08-21 15:49 ` Pierre-Louis Bossart
2020-10-13 4:50 ` Kuninori Morimoto
2020-10-15 14:32 ` Mark Brown
2020-10-15 23:04 ` 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=CAEnQRZCsy+QiMpCCRPNF-BUcjaT+UVE2B_a6Bd48f8tRqXTpOA@mail.gmail.com \
--to=daniel.baluta@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=spujar@nvidia.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).