From: Brian Austin <brian.austin@cirrus.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Cirrus Logic CS42L52 Low power codec
Date: Mon, 18 Feb 2008 10:34:33 -0600 [thread overview]
Message-ID: <1203352473.4063.22.camel@localhost.localdomain> (raw)
In-Reply-To: <20080218152259.GA7939@rakim.wolfsonmicro.main>
On Mon, Feb 18, 2008 at 08:45:49AM -0600, Brian Austin wrote:
> I was under the impression that the ASoc v1 ties the codec to a specific
> machine, and that v2 eliminates that need. Is that a correct
> assumption?
No, codec drivers shouldn't be tied to a specific platform in either
version - the main new feature in v2 from the point of view of codec
support is that it allows a machine to have more than one codec at once,
but that's not a change that affects the codec driver.
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?
Using s3c2410_defconfig will only let you select the devices that are added in the Kconfig for the s3c24xx.
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.
Thanks,
Brian
next prev parent reply other threads:[~2008-02-18 16:36 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 [this message]
2008-02-18 17:07 ` Timur Tabi
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=1203352473.4063.22.camel@localhost.localdomain \
--to=brian.austin@cirrus.com \
--cc=alsa-devel@alsa-project.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 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.