mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
To: Timur Tabi <timur@freescale.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Confused about audio drivers - where do I start?
Date: Fri, 23 Mar 2007 00:32:10 +0100	[thread overview]
Message-ID: <20070322233210.GA31582@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <46030AAD.4030509@freescale.com>

Hi,

On Thu, Mar 22, 2007 at 06:01:01PM -0500, Timur Tabi wrote:
> If I were to write a non-USB audio device driver from scratch (for new 
> hardware), what interface would I use?  Has ALSA become the official Linux 
> kernel audio subsystem?  Is there a specific device driver I should use as 
> a sample?

Yes, a driver should definitely be written against ALSA.

It's probably a good idea to use the most wide-spread card/driver close to the
hardware/functionality area of your new card as a sample driver,
the reasoning being that due to that card's wide use it's most likely that
all features are implemented as expected there.

And make sure to examine your new hardware about which sound card standards
it supports (AC-97, ...) which already have good generic support in ALSA.

When designing the mixer interface, definitely read ControlNames.txt and
name all mixer controls properly, since mixer apps have strongly differing
behaviour and may not work correctly without very strict and verbose control
naming. This implies wide testing with different mixer apps, too (gamix,
alsamixer, alsamixergui, gnome-alsamixer, kmix, aumix, ...).
Why I'm saying this? Because the first user report about my azt3328 driver
let me realize that some controls' naming was still broken despite having fixed
most of those a while ago...

Andreas Mohr

      parent reply	other threads:[~2007-03-22 23:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 23:01 Timur Tabi
2007-03-22 23:22 ` Randy Dunlap
2007-03-22 23:32 ` Andreas Mohr [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=20070322233210.GA31582@rhlx01.hs-esslingen.de \
    --to=andi@rhlx01.fht-esslingen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=timur@freescale.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

all inboxes | Powered by JetHome®