From: Timur Tabi <timur@freescale.com>
To: Ash Willis <ashwillis@programmer.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: I don't understand snd_pcm_ops
Date: Tue, 22 May 2007 11:17:08 -0500 [thread overview]
Message-ID: <46531784.70308@freescale.com> (raw)
In-Reply-To: <20070519000407.DCE031CE303@ws1-6.us4.outblaze.com>
Ash Willis wrote:
> Have you read "Writing an ALSA driver"? It generally describes ALSA drivers as
> they relate to PCI, and how to write them, but it does a good job at explaining
> the general ALSA driver architecture.
Unfortunately, most of my confusion stems from ASoC-specific issues. For instance, that
document says I should call snd_pcm_new(). But that's not true for ASoC drivers, because
I should really call snd_soc_new_pcms(), which in turn calls soc_new_pcm(), and *that*
function calls snd_pcm_new(). However, none of that explains why it's the *codec* driver
that is calling these functions. I don't understand why the codec driver is registering
new PCMs. Shouldn't the PCM driver be registering the codec?
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-05-22 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 0:04 I don't understand snd_pcm_ops Ash Willis
2007-05-22 16:17 ` Timur Tabi [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-18 23:13 Timur Tabi
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=46531784.70308@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=ashwillis@programmer.net \
/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.