From: <Codrin.Ciubotariu@microchip.com>
To: <broonie@kernel.org>
Cc: <perex@perex.cz>, <alsa-devel@alsa-project.org>,
<linux-kernel@vger.kernel.org>, <gustavoars@kernel.org>,
<mirq-linux@rere.qmqm.pl>, <tiwai@suse.com>,
<lgirdwood@gmail.com>
Subject: Re: [RFC PATCH 0/3] Separate BE DAI HW constraints from FE ones
Date: Fri, 16 Apr 2021 17:39:21 +0000 [thread overview]
Message-ID: <cba422f3-6400-2cad-9a04-369ce88eef20@microchip.com> (raw)
In-Reply-To: <20210416163131.GI5560@sirena.org.uk>
On 16.04.2021 19:31, Mark Brown wrote:
> On Fri, Apr 16, 2021 at 04:03:05PM +0000, Codrin.Ciubotariu@microchip.com wrote:
>
>> Thank you for the links! So basically the machine driver disappears and
>> all the components will be visible in user-space.
>
> Not entirely - you still need something to say how they're wired
> together but it'll be a *lot* simpler for anything that currently used
> DPCM.
Right, device-tree/acpi wiring is not enough...
>
>> If there is a list with the 'steps' or tasks to achieve this? I can try
>> to pitch in.
>
> Not really written down that I can think of. I think the next steps
> that I can think of right now are unfortunately bigger and harder ones,
> mainly working out a way to represent digital configuration as a graph
> that can be attached to/run in parallel with DAPM other people might
> have some better ideas though. Sorry, I appreciate that this isn't
> super helpful :/
>
I think I have good picture, a more robust card->dai_link, not with just
FEs and BEs ... I will try to monitor the alsa list more, see what other
people are working on. Thank you for your time!
Best regards,
Codrin
next prev parent reply other threads:[~2021-04-16 17:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 11:43 [RFC PATCH 0/3] Separate BE DAI HW constraints from FE ones Codrin Ciubotariu
2021-03-23 11:43 ` [RFC PATCH 1/3] pcm: use substream instead of runtime in snd_pcm_hw_rule_add() Codrin Ciubotariu
2021-03-23 11:43 ` [RFC PATCH 2/3] ASoC: soc-pcm: add hw_constraints for BE DAI links Codrin Ciubotariu
2021-03-23 11:43 ` [RFC PATCH 3/3] ASoC: soc-pcm: apply BE HW constraint rules Codrin Ciubotariu
2021-03-23 12:15 ` [RFC PATCH 0/3] Separate BE DAI HW constraints from FE ones Jaroslav Kysela
2021-03-23 14:18 ` Codrin.Ciubotariu
2021-04-14 14:58 ` Codrin.Ciubotariu
2021-04-15 16:17 ` Mark Brown
2021-04-15 16:56 ` Codrin.Ciubotariu
2021-04-15 17:25 ` Mark Brown
2021-04-16 16:03 ` Codrin.Ciubotariu
2021-04-16 16:31 ` Mark Brown
2021-04-16 16:47 ` Pierre-Louis Bossart
2021-04-16 18:55 ` Mark Brown
2021-04-16 19:39 ` Pierre-Louis Bossart
2021-04-19 15:07 ` Mark Brown
2021-04-16 17:39 ` Codrin.Ciubotariu [this message]
2021-03-23 19:25 ` Pierre-Louis Bossart
2021-03-24 9:51 ` Codrin.Ciubotariu
2021-03-24 15:28 ` Pierre-Louis Bossart
2021-03-24 17:12 ` Codrin.Ciubotariu
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=cba422f3-6400-2cad-9a04-369ce88eef20@microchip.com \
--to=codrin.ciubotariu@microchip.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gustavoars@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=perex@perex.cz \
--cc=tiwai@suse.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).