From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: jassi brar <jassisinghbrar@gmail.com>
Cc: kyungmin.park@samsung.com, alsa-devel@alsa-project.org,
Joonyoung Shim <jy0922.shim@samsung.com>
Subject: Re: Separate dma driver for cpu_dais
Date: Thu, 18 Feb 2010 09:52:49 +0000 [thread overview]
Message-ID: <20100218095249.GE3315@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1b68c6791002180142l422a9203se2a71cae5795d6a9@mail.gmail.com>
On Thu, Feb 18, 2010 at 06:42:26PM +0900, jassi brar wrote:
> On Thu, Feb 18, 2010 at 6:35 PM, Mark Brown
> > Could you please be more specific about what the workaround you are
> > referring to is? I'm genuinely not clear what you mean here.
> In order for a codec_dai to be used in more than one dai_link
> I check for its 'active' counter and call shutdown, startup, mute
> and schedule_delayed_work only if no other dai_link is
> actively using that codec_dai.
Where is the code you are talking about here? This sounds like driver
code...
next prev parent reply other threads:[~2010-02-18 9:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 2:39 Separate dma driver for cpu_dais jassi brar
2010-02-17 6:58 ` Joonyoung Shim
2010-02-17 7:24 ` jassi brar
2010-02-17 7:37 ` Joonyoung Shim
2010-02-17 10:52 ` Mark Brown
2010-02-17 12:15 ` jassi brar
2010-02-17 13:14 ` Mark Brown
2010-02-18 2:14 ` jassi brar
2010-02-18 9:35 ` Mark Brown
2010-02-18 9:42 ` jassi brar
2010-02-18 9:52 ` Mark Brown [this message]
2010-02-18 10:32 ` jassi brar
2010-02-18 10:57 ` Mark Brown
2010-02-18 11:59 ` jassi brar
2010-02-18 13:10 ` Mark Brown
2010-02-23 5:45 ` jassi brar
2010-02-23 10:37 ` Mark Brown
2010-02-19 9:48 ` jassi brar
2010-02-19 9:50 ` Mark Brown
2010-02-18 6:12 ` Joonyoung Shim
2010-02-18 9:42 ` Mark Brown
2010-02-17 10:42 ` Mark Brown
2010-02-17 12:13 ` jassi brar
2010-02-17 12:42 ` 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=20100218095249.GE3315@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jassisinghbrar@gmail.com \
--cc=jy0922.shim@samsung.com \
--cc=kyungmin.park@samsung.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.