All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Lai <plai@codeaurora.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>, Liam Girdwood <lrg@ti.com>
Subject: Re: Multicasting transfer mode
Date: Mon, 14 May 2012 13:21:41 -0700	[thread overview]
Message-ID: <4FB16955.70605@codeaurora.org> (raw)
In-Reply-To: <20120514085405.GI31985@opensource.wolfsonmicro.com>

On 5/14/2012 1:54 AM, Mark Brown wrote:
> On Mon, May 14, 2012 at 12:00:51AM -0700, Patrick Lai wrote:
>
>> The hardware I am working on has CODEC transfer microphone signal to
>> two SOCs simultaneously . In the machine driver, I have two dai-links
>
> This isn't something the framework supports.  You'd need to either
> implement the support or wait for someone else to do so.
>

Yes, I intended to implement framework support. However, I just want to
make sure I am not hijacking playback_active and capture_active flags
for unintended purpose. Base on existing code, playback_active is only
used for handling click and pop and capture_active flag is not used at
all.

Thanks
Patrick

>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel


-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

      reply	other threads:[~2012-05-14 20:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14  7:00 Multicasting transfer mode Patrick Lai
2012-05-14  8:54 ` Mark Brown
2012-05-14 20:21   ` Patrick Lai [this message]

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=4FB16955.70605@codeaurora.org \
    --to=plai@codeaurora.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.