From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
"Mark Brown" <broonie@kernel.org>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
Subject: Re: About Cleanup ASoC
Date: Tue, 24 May 2022 16:53:09 +0200 [thread overview]
Message-ID: <a5e3c40c-ea84-c2c4-54f9-70b4c509567e@intel.com> (raw)
In-Reply-To: <db3b90d3-d356-9a2a-7411-ccf487b25416@linux.intel.com>
On 2022-05-24 1:17 PM, Amadeusz Sławiński wrote:
> On 5/24/2022 6:40 AM, Kuninori Morimoto wrote:
>>
>> Hi ASoC
>> Cc Mark, Pierre-Louis, Cezary
>>
>> I have very interesting to clean up ASoC.
>> I think it is still very complex, thus, non flexible.
>> I'm thinking that we want to cleanup...
>>
>> - Component with multi Card connection
>> - fixed playback vs capture
>> - fixed CPU vs Codec
>> - DPCM connection vs normal connection
>>
>> About first topic,
>> I guess the biggest reason why we have limitation is
>> its connections.
>
> (...)
>
>> This makes the limitation which blocking multiple Card connections, I
>> think.
>>
>
> Hi,
>
> I would like to understand the problem here, before I start to discuss
> potential solutions. You seem to be saying that there is some kind of
> card<->component connection limitation? Is there specific use case you
> have in mind?
>
> Personally I don't see a reason for connecting component to multiple
> cards. Even if it would be possible it soon becomes problematic when you
> for example try to decide which card controls clock on component. As
> I've wrote I would like to first see some use case definition, before
> jumping into a rewrite.
Hello,
Thanks for your input Kuninori! Some questions first though :) On top of
what Amadeo already highlighted, I'd like to understand what do the
below three mean:
>> - fixed playback vs capture
>> - fixed CPU vs Codec
>> - DPCM connection vs normal connection
Especially the first two - what does 'fixed' stand here for?
Regards,
Czarek
next prev parent reply other threads:[~2022-05-24 14:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 4:40 About Cleanup ASoC Kuninori Morimoto
2022-05-24 11:17 ` Amadeusz Sławiński
2022-05-24 14:53 ` Cezary Rojewski [this message]
2022-05-25 2:54 ` Kuninori Morimoto
2022-05-25 16:11 ` Pierre-Louis Bossart
2022-05-26 2:13 ` Kuninori Morimoto
2022-05-26 9:57 ` Amadeusz Sławiński
2022-05-26 13:48 ` Pierre-Louis Bossart
2022-05-26 13:58 ` Mark Brown
2022-05-26 14:17 ` Cezary Rojewski
2022-05-26 14:45 ` Pierre-Louis Bossart
2022-05-27 6:50 ` Kuninori Morimoto
2022-05-31 12:25 ` Mark Brown
2022-06-01 6:13 ` Kuninori Morimoto
2022-06-02 9:26 ` Cezary Rojewski
2022-06-02 23:57 ` Kuninori Morimoto
2022-06-07 7:46 ` Cezary Rojewski
2022-06-09 0:07 ` Kuninori Morimoto
2022-05-27 8:38 ` Cezary Rojewski
2022-05-31 14:37 ` Pierre-Louis Bossart
2022-05-24 13:24 ` Mark Brown
2022-05-24 15:06 ` Cezary Rojewski
2022-05-24 16:11 ` Pierre-Louis Bossart
2022-05-25 3:02 ` 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=a5e3c40c-ea84-c2c4-54f9-70b4c509567e@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=pierre-louis.bossart@linux.intel.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.