From: Liam Girdwood <liam.girdwood@wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [PATCH 0/5] ASoC codecs
Date: Mon, 09 Oct 2006 17:57:47 +0100 [thread overview]
Message-ID: <1160413067.3235.62.camel@localhost.localdomain> (raw)
In-Reply-To: <s5h7izds7hq.wl%tiwai@suse.de>
On Fri, 2006-10-06 at 19:02 +0200, Takashi Iwai wrote:
> At Fri, 06 Oct 2006 17:07:26 +0100,
> Liam Girdwood wrote:
> >
> > On Fri, 2006-10-06 at 17:58 +0200, Takashi Iwai wrote:
> > > At Fri, 06 Oct 2006 16:47:30 +0100,
> > > Liam Girdwood wrote:
> > > >
> > > > On Wed, 2006-10-04 at 19:47 +0200, Takashi Iwai wrote:
> > > > > At Mon, 02 Oct 2006 17:15:15 +0100,
> > > > > Liam Girdwood wrote:
> > > > > >
> > > > > > This patch series will add initial ASoC codec support for the WM8731,
> > > > > > WM8750 and WM9712 codecs. It also adds support for AC97 codecs through a
> > > > > > generic AC97 codec driver (this connects any ASoC AC97 controller driver
> > > > > > to the std alsa ac97 codec driver). These codec drivers were chosen as
> > > > > > they are all working well and have good machine support (Zaurus).
> > > > > >
> > > > > > The ak4535, uda1380, wm8753 and wm9713 ASoC codec drivers are all beta
> > > > > > quality atm and will hopefully be submitted soon, after some further
> > > > > > testing.
> > > > >
> > > > > I got undefined soc_ac97_ops when I compile with your patches.
> > > > > A missing piece?
> > > > >
> > > >
> > > > It's shouldn't have been built (unless AC97 support was selected). I've
> > > > fixed this up in the codecs Kconfig and Makefile now (see new patch
> > > > 5/5).
> > >
> > > But I couldn't find the definition of soc_ac97_ops in your patches.
> > > Which patch does include this?
> > >
> >
> > This is supplied by any AC97 controller driver, however it's not in the
> > AT91 series as AC97 is not supported. It will appear in the pxa2xx AC97
> > driver patch next week.
> >
> > It's only used by the AC97 codec drivers and the soc-core (and only
> > *now* when SOC_AC97_ is selected by the build system).
>
> OK. Now I merged all ASoC-related patches you've posted to ALSA HG
> tree. Please check out whether it's OK for you.
>
Thanks, It all seems fine. :)
Liam
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2006-10-09 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 16:15 [PATCH 0/5] ASoC codecs Liam Girdwood
2006-10-04 17:47 ` Takashi Iwai
2006-10-06 15:47 ` Liam Girdwood
2006-10-06 15:58 ` Takashi Iwai
2006-10-06 16:07 ` Liam Girdwood
2006-10-06 17:02 ` Takashi Iwai
2006-10-09 16:57 ` Liam Girdwood [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=1160413067.3235.62.camel@localhost.localdomain \
--to=liam.girdwood@wolfsonmicro.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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