All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.girdwood@wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Nicolas Pitre <nico@cam.org>,
	alsa-devel@lists.sourceforge.net,
	Bill Gatliff <bgat@billgatliff.com>
Subject: Re: [PATCH] AC97 bus interface for ad-hoc drivers
Date: Fri, 29 Jul 2005 12:20:40 +0100	[thread overview]
Message-ID: <1122636040.3117.28.camel@localhost.localdomain> (raw)
In-Reply-To: <s5h4qaddh5w.wl%tiwai@suse.de>

On Fri, 2005-07-29 at 12:45 +0200, Takashi Iwai wrote:
> At Thu, 28 Jul 2005 21:26:39 +0100,
> Liam Girdwood wrote:

> > 
> > In this scenario SND_SOME_DRIVER selects SND_AC97_CODEC selects
> > SND_AC97_BUS and I could never get a SND_AC97_BUS=m or otherwise in
> > my .config. I was only ever successful by adding the select SND_AC97_BUS
> > line to SND_SOME_DRIVER.
> 
> Is it a PCI driver?  Since SND_AC97_CODEC and SND_AC97_BUS is in
> pci/Kconfig, it might the case that it's be selected only when
> PCI!=n.
> 
> 

It's an Arm (PXA27x) based driver, hence PCI=n.

You are correct. I had unsuccessfully tried the config SND_AC97_BUS out
with the PCI=n clause. It only works when _both_ SND_AC97_CODEC and
SND_AC97_BUS are out with PCI=n.

If nobody objects, I can resubmit with the SND_AC97_CODEC out with the
PCI=n in sound/pci/Kconfig. Will this cause any problems for other
cards ? 

> > I now don't think that the "select SND_PCM" is having any effect in the
> > AC97_CODEC config, although it still builds fine when remove it.
> 
> Hmm, we didn't have problems with other similar cases...

It was being included by the other Arm drivers.

Liam 



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  reply	other threads:[~2005-07-29 11:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 12:20 [PATCH] AC97 bus interface for ad-hoc drivers Liam Girdwood
2005-07-27 11:10 ` Takashi Iwai
2005-07-27 13:05   ` Nicolas Pitre
2005-07-27 13:18     ` Takashi Iwai
2005-07-27 13:43       ` Liam Girdwood
2005-07-28 20:26     ` Liam Girdwood
2005-07-29 10:45       ` Takashi Iwai
2005-07-29 11:20         ` Liam Girdwood [this message]
2005-07-29 11:27           ` Takashi Iwai
2005-07-29 12:51             ` Liam Girdwood
2005-07-29 15:19               ` Takashi Iwai
2005-07-31 14:26                 ` Liam Girdwood

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=1122636040.3117.28.camel@localhost.localdomain \
    --to=liam.girdwood@wolfsonmicro.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=bgat@billgatliff.com \
    --cc=nico@cam.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.