From: <Codrin.Ciubotariu@microchip.com>
To: <broonie@kernel.org>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<lgirdwood@gmail.com>, <tiwai@suse.com>, <perex@perex.cz>,
<lars@metafoo.de>
Subject: Re: [RFC PATCH] ASoC: pcm_dmaengine: Add support for BE DAIs
Date: Fri, 11 Dec 2020 18:00:55 +0000 [thread overview]
Message-ID: <b98d9b89-268b-5a4f-57bc-b7f95d6c81a4@microchip.com> (raw)
In-Reply-To: <20201208193156.GJ6686@sirena.org.uk>
On 08.12.2020 21:31, Mark Brown wrote:
> On Tue, Dec 08, 2020 at 07:26:35PM +0000, Codrin.Ciubotariu@microchip.com wrote:
>
>> I do not know too much about the dummy PCM. It seems like it is creating
>> a card without DPCM links and fakes a buffer, which is not quite what I
>> need. I will investigate more.
>
> Right, that's what I was imagining the second runtime you proposed
> looking like.
>
I don't need the whole struct snd_pcm_runtime, only struct
snd_pcm_hardware, at least for now. I looked some more and a suitable
place would be struct snd_soc_dpcm, since it is created at runtime and
used anyway to characterize a FE <-> BE link. What do you think?
Also, I noticed that the HW constraints added by a DAI driver (a codec
for example) are added to PCM's runtime->hw_constraints, even if the DAI
driver is part of a BE. Shouldn't these constraints be applied only to
BE and eventually merge them to FE (struct snd_pcm_hardware) if
dai_link->dpcm_merged_* are set?
Best regards,
Codrin
next prev parent reply other threads:[~2020-12-11 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 8:58 [RFC PATCH] ASoC: pcm_dmaengine: Add support for BE DAIs Codrin Ciubotariu
2020-12-08 17:04 ` Mark Brown
2020-12-08 19:26 ` Codrin.Ciubotariu
2020-12-08 19:31 ` Mark Brown
2020-12-11 18:00 ` Codrin.Ciubotariu [this message]
2020-12-14 17:19 ` Mark Brown
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=b98d9b89-268b-5a4f-57bc-b7f95d6c81a4@microchip.com \
--to=codrin.ciubotariu@microchip.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).