[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150430201207.GK22845@sirena.org.uk>
Date: Thu, 30 Apr 2015 21:12:07 +0100
From: Mark Brown <broonie@...nel.org>
To: Koro Chen <koro.chen@...iatek.com>
Cc: Sascha Hauer <s.hauer@...gutronix.de>, robh+dt@...nel.org,
matthias.bgg@...il.com, perex@...ex.cz, tiwai@...e.de,
srv_heupstream@...iatek.com, linux-mediatek@...ts.infradead.org,
galak@...eaurora.org, lgirdwood@...il.com,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [RESEND RFC PATCH 1/3] ASoC: mediatek: Add binding support for
AFE driver
On Wed, Apr 22, 2015 at 11:17:20AM +0800, Koro Chen wrote:
> If using DPCM, it seems the most suitable FE DAIs will be memif, and
> external interface like I2S should be BE DAIs. Do you think it is
> suitable for our memif to be FE DAIs? Then which memif to used can be
> described in a machine driver's FE DAIs. But I think this has a problem
> that our memif is one-direction, playback or capture. So the binded pcm
> device cannot have playback and capture capability together. May it
> cause trouble for user space apps that assumes there will be pcmC0D0p,
> pcmC0D0c?
I think the only userspace application you really have to worry about
here is PulseAudio which (at least with UCM) should be able to cope
since it needs to handle things like USB microphones. I think
everything else I can think of can either cope or has to handle the same
use cases as PulseAudio does so should have support.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists