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

Hi,

The hardware I am working on has CODEC transfer microphone signal to
two SOCs simultaneously . In the machine driver, I have two dai-links
defined for main SOC and secondary SOC. Both DAI-LINKs include same
CODEC DAI. As long as only one dai-link is being accessed at a time,
thing is fine. However, when two dai-links are accessed at the same
time and one dai-link goes down, soc framework tears down the CODEC DAI
as it does not take account of same CODEC DAI is being used by other
dai-link. I see playback_active and capture_active being defined in
struct snd_soc_dai. I am thinking about using these flags to address
this problem. Is it the right approach? Is there precedence being
addressed with different approach? Also, I am referring to kernel 3.4
rc7. In soc-dai.h, playback_active and capture active are defined as
  unsigned int capture_active:1;          /* stream is in use */
   unsigned int playback_active:1;         /* stream is in use */

However, in soc-pcm.c, playback_active and capture_active are being
incremented and decremented instead of set and clear. If I use these
flags to address my problem, I am going to increase number of bits.

Thanks
Patrick

-- 
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  7:00 UTC|newest]

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

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=4FB0ADA3.3020304@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.