From: Ben Dooks <ben-linux@fluff.org>
To: Wan ZongShun <mcuos.com@gmail.com>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
zswan@marvell.com
Subject: Re: about ALC203 linux driver
Date: Mon, 10 May 2010 05:05:21 +0100 [thread overview]
Message-ID: <20100510040521.GF6684@trinity.fluff.org> (raw)
In-Reply-To: <AANLkTik0GudetGLF9hF56_VV_tNci8wX0S67gAWDIayq@mail.gmail.com>
On Sun, May 09, 2010 at 11:34:28PM +0800, Wan ZongShun wrote:
> Dear Mark,
>
>
> 2010/5/9 Mark Brown <broonie@opensource.wolfsonmicro.com>:
> > On Sun, May 09, 2010 at 10:40:07PM +0800, Wan ZongShun wrote:
> >
> >> At present, there is a ALC203 AC97 codec in my Winbond ARM board, and
> >> I am programming
> >> the audio driver based on ALSA, Who can tell me whether the current
> >> ALSA is supporting
> >> the ALC203 driver?how to enable it?
> >
> > You need a driver for the AC97 controller your system is using (for most
> > ARM systems this is part of the CPU). Since AC97 provides a standard
> > register interface for CODECs Linux does not require specific support
> > for individual AC97 CODECs in order to get core functionality working.
> >
>
> There is AC97 support for my chip, and I have implemented the nuc900_ac97.c
> ,nuc900_pcm.c and machine board c file drivers.The three main
> structure definitions
> as following:
does you SoC require any other configurations in other blocks that
may aslo affect this, such as gpio configuratioon for the ac97 pins or
some sort of clock setup?
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
prev parent reply other threads:[~2010-05-10 4:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-09 14:40 about ALC203 linux driver Wan ZongShun
2010-05-09 14:49 ` Mark Brown
2010-05-09 15:34 ` Wan ZongShun
2010-05-09 17:52 ` Mark Brown
2010-05-10 1:24 ` [alsa-devel] " Vincent Wan
2010-05-10 4:05 ` Ben Dooks [this message]
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=20100510040521.GF6684@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mcuos.com@gmail.com \
--cc=zswan@marvell.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).