From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752018AbbEDB5e (ORCPT ); Sun, 3 May 2015 21:57:34 -0400 Received: from mailgw02.mediatek.com ([210.61.82.184]:38397 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751983AbbEDB50 (ORCPT ); Sun, 3 May 2015 21:57:26 -0400 X-Listener-Flag: 11101 Subject: Re: [RESEND RFC PATCH 1/3] ASoC: mediatek: Add binding support for AFE driver From: Koro Chen To: Mark Brown CC: Sascha Hauer , , , , , , , , , , , , In-Reply-To: <20150430201207.GK22845@sirena.org.uk> References: <1428653649-38200-1-git-send-email-koro.chen@mediatek.com> <1428653649-38200-2-git-send-email-koro.chen@mediatek.com> <20150418173407.GE26185@sirena.org.uk> <20150420043747.GH6325@pengutronix.de> <20150420204849.GJ14892@sirena.org.uk> <1429672640.14162.55.camel@mtksdaap41> <20150430201207.GK22845@sirena.org.uk> Content-Type: text/plain; charset="UTF-8" Date: Mon, 4 May 2015 09:57:19 +0800 Message-ID: <1430704639.4497.6.camel@mtksdaap41> MIME-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit X-MTK: N Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Koro Chen Subject: Re: [RESEND RFC PATCH 1/3] ASoC: mediatek: Add binding support for AFE driver Date: Mon, 4 May 2015 09:57:19 +0800 Message-ID: <1430704639.4497.6.camel@mtksdaap41> References: <1428653649-38200-1-git-send-email-koro.chen@mediatek.com> <1428653649-38200-2-git-send-email-koro.chen@mediatek.com> <20150418173407.GE26185@sirena.org.uk> <20150420043747.GH6325@pengutronix.de> <20150420204849.GJ14892@sirena.org.uk> <1429672640.14162.55.camel@mtksdaap41> <20150430201207.GK22845@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150430201207.GK22845-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Mark Brown Cc: Sascha Hauer , robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, perex-/Fr2/VpizcU@public.gmane.org, tiwai-l3A5Bk7waGM@public.gmane.org, srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org, linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org List-Id: devicetree@vger.kernel.org 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 devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: koro.chen@mediatek.com (Koro Chen) Date: Mon, 4 May 2015 09:57:19 +0800 Subject: [RESEND RFC PATCH 1/3] ASoC: mediatek: Add binding support for AFE driver In-Reply-To: <20150430201207.GK22845@sirena.org.uk> References: <1428653649-38200-1-git-send-email-koro.chen@mediatek.com> <1428653649-38200-2-git-send-email-koro.chen@mediatek.com> <20150418173407.GE26185@sirena.org.uk> <20150420043747.GH6325@pengutronix.de> <20150420204849.GJ14892@sirena.org.uk> <1429672640.14162.55.camel@mtksdaap41> <20150430201207.GK22845@sirena.org.uk> Message-ID: <1430704639.4497.6.camel@mtksdaap41> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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.