mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: Geoffrey Wossum <geoffrey@pager.net>,
	kernel@avr32linux.org, linux-kernel@vger.kernel.org
Subject: Re: AT32 ASoC Driver Patches on alsa-devel
Date: Fri, 6 Jun 2008 13:07:35 +0100	[thread overview]
Message-ID: <20080606120733.GB24872@sirena.org.uk> (raw)
In-Reply-To: <20080606112915.4b1d5d42@hskinnemo-gx745.norway.atmel.com>

On Fri, Jun 06, 2008 at 11:29:15AM +0200, Haavard Skinnemoen wrote:

> But I would have thought that if you have a PC sound card with an
> on-board i2s bus and a standard codec, you could create a board driver
> by simply hooking the different parts together, possibly with a custom
> i2s bus driver?

If the card has been built in that way then yes, you could do that.

> Geoffrey Wossum <geoffrey@pager.net> wrote:

> >  - I think PC sound cards tend to be black boxes regarding power consumption, 
> > especially those white box cards you can get at Fry's and similar places.   

> Right...so it's a matter of documentation. I suspect those white box
> cards still use cheap, standard hardware under the hood, though maybe
> that fact is pretty well hidden.

There may just not be the control exposed - there's quite a lot of parts
intended for simple applications which may only offer a few bits of
control for things like mute done via setting levels on pins.

> away. For example, a particular AC97 codec chip may be used with a
> different driver depending on whether it's soldered on a PC motherboard
> or some embedded board. That feels wrong to me.

That should really only be required if you're using features which go
substantially outside the AC97 spec (modulo perhaps needing to make
ac97.c glue more stuff together).

  reply	other threads:[~2008-06-06 12:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200806050851.47319.geoffrey@pager.net>
2008-06-05 14:22 ` Haavard Skinnemoen
2008-06-05 15:00   ` Geoffrey Wossum
2008-06-05 16:24     ` Haavard Skinnemoen
2008-06-05 16:54       ` Takashi Iwai
2008-06-05 17:06         ` Haavard Skinnemoen
2008-06-06  6:15           ` Takashi Iwai
2008-06-05 17:10       ` Geoffrey Wossum
2008-06-06  9:29         ` Haavard Skinnemoen
2008-06-06 12:07           ` Mark Brown [this message]
2008-06-06 14:32           ` Geoffrey Wossum
2008-06-05 15:22   ` Mark Brown
2008-06-05 16:40     ` Haavard Skinnemoen
2008-06-06 11:37       ` 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=20080606120733.GB24872@sirena.org.uk \
    --to=broonie@sirena.org.uk \
    --cc=geoffrey@pager.net \
    --cc=haavard.skinnemoen@atmel.com \
    --cc=kernel@avr32linux.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®