From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Barry Song <21cnbao@gmail.com>
Cc: uclinux-dist-devel@blackfin.uclinux.org, "Cai,
Cliff" <Cliff.Cai@analog.com>,
alsa-devel@alsa-project.org,
Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: dev_* output functions and ASoC codecs
Date: Tue, 13 Oct 2009 11:14:45 +0100 [thread overview]
Message-ID: <20091013101445.GA29177@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <3c17e3570910130309r3ffed293g9cc8f9bd0c845d4@mail.gmail.com>
On Tue, Oct 13, 2009 at 06:09:07PM +0800, Barry Song wrote:
> Another issue is that there is only one global soc_ac97_ops in the
> whole system. In case there are two different ac97 ports, how to
> handle?
> Even though the two ac97 ports are same, how could CPU DAI related
> private data can be given to snd_ac97 to let it use that data to
> execute different operations? It seems snd_ac97 is only attached to
> codec.
I've no current plan to work on multiple AC97 controllers support within
ASoC except in so far as it falls out of other work - I've never
encountered an embedded system with multiple AC97 controllers so it's a
somewhat academic issue. Patches welcome, though I'd expect it'd be
sensible to wait until multi-card support is present.
next prev parent reply other threads:[~2009-10-13 10:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 0:18 dev_* output functions and ASoC codecs Mike Frysinger
2009-10-06 10:20 ` Mark Brown
2009-10-12 2:26 ` Barry Song
2009-10-12 9:36 ` Mark Brown
2009-10-12 10:34 ` Barry Song
2009-10-12 10:48 ` Mark Brown
2009-10-12 13:20 ` Barry Song
2009-10-12 14:20 ` Mark Brown
2009-10-13 10:09 ` Barry Song
2009-10-13 10:14 ` Mark Brown [this message]
2009-10-20 5:27 ` Barry Song
2009-10-20 9:52 ` 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=20091013101445.GA29177@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=21cnbao@gmail.com \
--cc=Cliff.Cai@analog.com \
--cc=alsa-devel@alsa-project.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier.adi@gmail.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