From: Sameer Pujar <spujar@nvidia.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: sharadg@nvidia.com, Linux-ALSA <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
jonathanh@nvidia.com
Subject: Re: More Generic Audio Graph Sound Card idea
Date: Tue, 25 Aug 2020 11:12:50 +0530 [thread overview]
Message-ID: <2d9140c7-7cba-34d9-d4b7-c9f9f395d9e7@nvidia.com> (raw)
In-Reply-To: <87r1rvwbsd.wl-kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
>>> But, I guess new driver 1st version is focus to
>>> detecting normal-link and DPCM-link only.
>> Do you plan to propose something like enum for card2 and has scope for
>> extension, where link type can be normal/DPCM/codec-to-codec/etc., ?
>> Since there are so many board variants and may have some specific
>> requirements, I am wondering being able to detect link type from DT
>> should be the only motivation for a new driver.
> I'm now thinking that new one can detect normal-link, DPCM-link,
> multi-CPU / multi-Codec, Codec-to-Codec as normal audio-graph feature.
> And has .hook callback for Eeach board specific feature.
> see my previous mail which was To:Pierre-Louis
> But, it is still under idea, not yet fixed.
If we plan to go this way, I think we need to consider board specific
configuration at init time and one at runtime. In that case there could
be multiple compatibles that would get added to the driver and various
other requirements can be managed with behavioral flags instead from DT?
Thanks,
Sameer.
next prev parent reply other threads:[~2020-08-25 5:43 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 [this message]
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=2d9140c7-7cba-34d9-d4b7-c9f9f395d9e7@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sharadg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.