On Fri, Dec 11, 2020 at 06:00:55PM +, codrin.ciubota...@microchip.com wrote:
> 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
On 08.12.2020 21:31, Mark Brown wrote:
> On Tue, Dec 08, 2020 at 07:26:35PM +, codrin.ciubota...@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
On 08.12.2020 19:04, Mark Brown wrote:
> On Wed, Dec 02, 2020 at 10:58:38AM +0200, Codrin Ciubotariu wrote:
>
>> This patch is more or less incomplete for the described scenario. This
>> is because DMAengine's pcm->config is ignored for the BE DAI link, so
>> runtime->hw is not updated. Also,
On Tue, Dec 08, 2020 at 07:26:35PM +, codrin.ciubota...@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
On Wed, Dec 02, 2020 at 10:58:38AM +0200, Codrin Ciubotariu wrote:
> This patch is more or less incomplete for the described scenario. This
> is because DMAengine's pcm->config is ignored for the BE DAI link, so
> runtime->hw is not updated. Also, since pcm_construct/destruct are not
> called,
Considering the bellow scenarios:
/- Gen DMA engine -\
48KHz *** 44.1KHz ***
*
PCM0 <-FE DAI-> * FE * <-> * DSP * <-BE DAI-> * * * * *
*
* Ring *
6 matches
Mail list logo
