[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1430704639.4497.6.camel@mtksdaap41>
Date: Mon, 4 May 2015 09:57:19 +0800
From: Koro Chen <koro.chen@...iatek.com>
To: Mark Brown <broonie@...nel.org>
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 Thu, 2015-04-30 at 21:12 +0100, Mark Brown wrote:
> 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.
Thank you very much for the feedback, I will try DPCM.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists