From: Timur Tabi <timur@freescale.com>
To: Brian Austin <brian.austin@cirrus.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Cirrus Logic CS42L52 Low power codec
Date: Mon, 18 Feb 2008 11:07:28 -0600 [thread overview]
Message-ID: <47B9BB50.8080408@freescale.com> (raw)
In-Reply-To: <1203352473.4063.22.camel@localhost.localdomain>
Brian Austin wrote:
> Since the codecs are not tied to the machine, the user must then add to the Kconfig of the
> ARCH to select which codec they want to use?
Yes. For most ASoC V1 platforms, the use selects a Kconfig for his platform,
and *that* Kconfig selects the codec. Example:
config SND_SOC_MPC8610_HPCD
bool "ALSA SoC support for the Freescale MPC8610 HPCD board"
depends on SND_SOC_MPC8610
select SND_SOC_CS4270
^^^^^^^^^^^^^^^^^^^^^
> If the codec isn't tied to the machine, why can't we select from a list of supported codecs?
> Just trying to get a better understanding of how this works.
The codec is not tied to the machine, but the machine is tied to the codec.
That is, in ASoC V1, the machine driver must know about the codec driver at
compile time.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-02-18 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 14:17 Cirrus Logic CS42L52 Low power codec Brian Austin
2008-02-18 14:36 ` Mark Brown
2008-02-18 14:45 ` Brian Austin
2008-02-18 15:06 ` Timur Tabi
2008-02-18 15:22 ` Mark Brown
2008-02-18 16:34 ` Brian Austin
2008-02-18 17:07 ` Timur Tabi [this message]
2008-02-18 17:35 ` Ben Dooks
2008-02-18 17:58 ` Mark Brown
2008-02-18 18:07 ` Brian Austin
2008-02-18 19:05 ` 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=47B9BB50.8080408@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.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 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.