From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Mark Brown <broonie@kernel.org>
Cc: Sameer Pujar <spujar@nvidia.com>,
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: 04 Sep 2020 08:51:33 +0900 [thread overview]
Message-ID: <87d032mnfo.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <878se4zybn.wl-kuninori.morimoto.gx@renesas.com>
Hi Mark
Cc Sameer
> > Having an audio-graph-card2 isn't ideal but may be required at least
> > during development :/ Ideally we'd be able to have the new driver parse
> > both binding formats (or rather, have the new binding format be new use
> > cases for the same binding format) and only use -card2 while it's in
> > development.
>
> If you want to update current audio-graph-card without creating new
> audio-graph-card2, I'm OK about it. But need adjusting / agreement.
>
> Current audio-graph-card "DSP" user is only me, and I'm using it only locally.
> Thus upstream doesn't get damage if I removed "audio-graph-scu-card"
> (= DSP use case) support.
>
> OTOH, Sameer is posting patch for "-cc-" support. If it was accepted
> and he used it on upstream (= on tegra),
> keeping compatibility will be very difficult and/or code will be very confusable.
>
> If Sameer can OK and wait new audio-graph-card, maybe we have no compatibility issue.
> But in such case, 1st version of new audio-graph-card might be not enough for him.
> Sameer need to waiting / testing / adjusting / etc, etc...
The problem I'm feeling is that new card (= let's call it as card2 here) and
Sameer's posting "-cc-" are conflicted / no-compatibility.
It expands card1 DPCM detection.
The good things having "-cc-" is that he can use it immediately.
the bad things is that it is dificult to keep compatibility between "card1 + -cc-" and "card2".
Creating card2 for development purpose is very welcome for me, and card1 user :)
But after that, if we want to merge card1 and card2, we need to drop "-cc-" support unfortunately.
If we want to keep "-cc-", we need to have both card1 / card2.
So, how to handle it ?
Thank you for your help !!
Best regards
---
Kuninori Morimoto
next prev parent reply other threads:[~2020-09-03 23:52 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
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 [this message]
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=87d032mnfo.wl-kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--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).