From: Steve Calfee <stevecalfee@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Connecting a codec to an i2c codec driver.
Date: Thu, 24 Mar 2011 12:56:27 -0700 [thread overview]
Message-ID: <4D8BA1EB.2080407@gmail.com> (raw)
In-Reply-To: <20110323133013.GB25754@opensource.wolfsonmicro.com>
On 03/23/11 06:30, Mark Brown wrote:
> On Wed, Mar 23, 2011 at 06:22:59AM -0700, Steve Calfee wrote:
>> On Wed, Mar 23, 2011 at 4:07 AM, Mark Brown
>
>>> You need to write a machine driver for your board describing how the
>>> CODEC is connected to the CPU and other components in your system.
>
>> Great, can you give me a pointer to a sample arm source code
>> in the 2.6.38 kernel?
>
> There are *many* example machine drivers under sound/soc. Look for a
> driver for a machine relevant to your CPU (eg, a reference board).
Thanks, that helps.
Any tips on how to turn on the debug printouts in the alsa and device
systems? Do I recompile the kernel with new options etc? I already
lowered the /proc/sys/kernel/printk level to 8.
Regards, Steve
next prev parent reply other threads:[~2011-03-24 19:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 14:12 how to create alsa nodes? loody
2011-03-17 14:26 ` Clemens Ladisch
2011-03-18 9:03 ` loody
2011-03-23 0:40 ` Connecting a codec to an i2c codec driver Steve Calfee
2011-03-23 11:07 ` Mark Brown
2011-03-23 13:22 ` Steve Calfee
2011-03-23 13:30 ` Mark Brown
2011-03-24 19:56 ` Steve Calfee [this message]
2011-03-25 11:43 ` Mark Brown
2013-02-12 8:17 ` emi62 (may be slightly off-topic) Karl Grill
2013-02-15 14:44 ` Takashi Iwai
2013-02-15 15:28 ` Monty Montgomery
2013-02-15 15:37 ` Monty Montgomery
2013-02-15 16:07 ` Takashi Iwai
2013-02-15 16:14 ` Monty Montgomery
2013-02-15 16:26 ` Takashi Iwai
2013-12-11 0:04 ` Monty Montgomery
2013-12-11 14:34 ` Takashi Iwai
2013-12-12 7:32 ` Monty Montgomery
2013-12-12 17:11 ` Takashi Iwai
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=4D8BA1EB.2080407@gmail.com \
--to=stevecalfee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).