From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jassi Brar <jassi.brar@samsung.com>
Cc: alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: Allow mulitple usage count of codec and cpu dai
Date: Fri, 26 Feb 2010 09:17:52 +0000 [thread overview]
Message-ID: <1267175872.3212.7.camel@odin> (raw)
In-Reply-To: <1267143152-15861-1-git-send-email-jassi.brar@samsung.com>
On Fri, 2010-02-26 at 09:12 +0900, Jassi Brar wrote:
> If we are to have a snd_soc_dai i.e, cpu_dai and codec_dai, shared among two
> or more dai_links we need to log the number of active users of the dai.
> For that, we change semantics of the snd_soc_dai.active flag from indicator
> to reference counter.
>
> Signed-off-by: Jassi Brar <jassi.brar@samsung.com>
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-02-26 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 0:12 [PATCH] ASoC: Allow mulitple usage count of codec and cpu dai Jassi Brar
2010-02-26 9:17 ` Liam Girdwood [this message]
2010-02-26 11:20 ` 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=1267175872.3212.7.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jassi.brar@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 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).