All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Ramya Desai <ramya.desai@gmail.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org
Subject: Re: Writing a driver for Sound Card
Date: Tue, 23 Nov 2010 15:27:28 +0100	[thread overview]
Message-ID: <4CEBCF50.1080108@ladisch.de> (raw)
In-Reply-To: <AANLkTins58fB33LiFbNpbgAwKWDBtKs71=9ae3D+i+V4@mail.gmail.com>

Ramya Desai wrote:
> I have a doubt about the Linux sound driver architecture. I need to
> develop the driver with mixer, player, recorder, MIDI etc. components.
> Do I need to develop these components in single driver OR Do I need to
> develop as a individual component (one driver for one component).

You can do this however you want; ALSA doesn't impose any restriction.

Many drivers choose put the code for different components in separate
source files because the components are actually independent.

When a driver uses other modules, this is usually because that hardware
is common for multiple sound cards (e.g., most MIDI interfaces are
compatible with the Roland MPU-401).

> I looked into the /usr/src/linux-2.6.35/sound directory. I did not
> understand it completely. Is there any driver (sample) which I can go
> through?

The basic driver structure is explained in the documentation; most of
the additional code in drivers handles the quirks of actual hardware
and would not be very helpful for you.  Do you have any specific
questions?

Please tell us more about the architecture of your hardware.


Regards,
Clemens

  reply	other threads:[~2010-11-23 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 12:47 Writing a driver for Sound Card Ramya Desai
2010-11-23 14:27 ` Clemens Ladisch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-11-23 12:33 Ramya Desai
2010-11-23 23:27 ` 

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=4CEBCF50.1080108@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=ramya.desai@gmail.com \
    --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.