linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: koro.chen@mediatek.com (Koro Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND RFC PATCH 1/3] ASoC: mediatek: Add binding support for AFE driver
Date: Mon, 4 May 2015 09:57:19 +0800	[thread overview]
Message-ID: <1430704639.4497.6.camel@mtksdaap41> (raw)
In-Reply-To: <20150430201207.GK22845@sirena.org.uk>

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.
  

  reply	other threads:[~2015-05-04  1:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1428653649-38200-1-git-send-email-koro.chen@mediatek.com>
     [not found] ` <1428653649-38200-2-git-send-email-koro.chen@mediatek.com>
2015-04-18 17:34   ` [RESEND RFC PATCH 1/3] ASoC: mediatek: Add binding support for AFE driver Mark Brown
2015-04-20  4:37     ` Sascha Hauer
2015-04-20 20:48       ` Mark Brown
2015-04-21  9:49         ` Sascha Hauer
2015-04-21 10:14           ` Mark Brown
2015-04-21 10:15           ` Koro Chen
2015-04-21 10:56             ` Mark Brown
2015-04-22  3:17         ` Koro Chen
2015-04-30 20:12           ` Mark Brown
2015-05-04  1:57             ` Koro Chen [this message]
     [not found] ` <1428653649-38200-3-git-send-email-koro.chen@mediatek.com>
2015-04-18 17:37   ` [RESEND RFC PATCH 2/3] ASoC: mediatek: Add AFE connection control Mark Brown
2015-04-20  4:50     ` Sascha Hauer
2015-04-20 20:52       ` Mark Brown
2015-04-21  5:50         ` Sascha Hauer
2015-04-21 10:15           ` Mark Brown
     [not found] ` <1428653649-38200-4-git-send-email-koro.chen@mediatek.com>
2015-04-18 17:51   ` [RESEND RFC PATCH 3/3] ASoC: mediatek: Add AFE platform driver Mark Brown
2015-04-20  6:22     ` Koro Chen
2015-04-20 20:55       ` Mark Brown
2015-04-21  2:27         ` Koro Chen
2015-04-21 10:05           ` 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=1430704639.4497.6.camel@mtksdaap41 \
    --to=koro.chen@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).