From: Barry Song <21cnbao@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: uclinux-dist-devel@blackfin.uclinux.org,
alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: bug in spi and i2c dual buses codecs
Date: Mon, 29 Mar 2010 18:29:45 +0800 [thread overview]
Message-ID: <3c17e3571003290329p1c04b649uc6c3e36f21d79232@mail.gmail.com> (raw)
In-Reply-To: <20100329094938.GB29441@rakim.wolfsonmicro.main>
On Mon, Mar 29, 2010 at 5:49 PM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
>
> On Mon, Mar 29, 2010 at 02:24:28PM +0800, Barry Song wrote:
>
> > In fact, if any bus is compiled as module and code is built-in, link error
> > will be reported.
>
> Yes, this is expected behaviour. It's not been a practical problem -
> the combination of audio built in and one of the buses modular is far
> from common.
Ok. if so, practically, people should either built-in all, or keep
codec driver as module if anyone of i2c and spi is module.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2010-03-29 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 6:24 bug in spi and i2c dual buses codecs Barry Song
2010-03-29 9:49 ` Mark Brown
2010-03-29 10:29 ` Barry Song [this message]
2010-03-29 18:25 ` [Uclinux-dist-devel] " Mike Frysinger
[not found] ` <8bd0f97a1003291125t77aa762eida59cd4a112927ae-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-29 18:48 ` [alsa-devel] " 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=3c17e3571003290329p1c04b649uc6c3e36f21d79232@mail.gmail.com \
--to=21cnbao@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
/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).