All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Eric B??nard <eric@eukrea.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ASoC: Hooking a TI CODEC to a i.MX27 MCU
Date: Fri, 28 May 2010 12:08:07 +0100	[thread overview]
Message-ID: <20100528110805.GA9917@sirena.org.uk> (raw)
In-Reply-To: <4BFF5AC7.3060409@eukrea.com>

On Fri, May 28, 2010 at 07:55:19AM +0200, Eric B??nard wrote:
> Hi Stuart,

Don't drop CCs from mailing list postings, you should always maintain
CCs for kernel related lists.

> I'll try to find our I2C init sequence and send it to you as this was 
> the hardest part of the thing to get the codec running.

Under Linux you'd normally not be using just a hard coded sequence of
I2C writes...

  reply	other threads:[~2010-05-28 11:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24  7:49 ASoC: Hooking a TI CODEC to a i.MX27 MCU Stuart Longland
2010-05-24 10:49 ` Liam Girdwood
2010-05-25  0:41   ` Stuart Longland
2010-05-25  2:26     ` Stuart Longland
2010-05-25  3:26       ` Stuart Longland
2010-05-25 16:46       ` gnutoo
2010-05-26 13:21         ` Stuart Longland
2010-05-27  0:47           ` Mark Brown
2010-05-28  2:06             ` Stuart Longland
2010-05-28  5:55               ` Eric Bénard
2010-05-28 11:08                 ` Mark Brown [this message]
2010-05-28 13:10                   ` Eric Bénard
2010-06-01  3:30                 ` Stuart Longland
2010-06-01  5:07                   ` Stuart Longland
2010-06-01 11:32                     ` Stuart Longland
2010-06-03 11:14                       ` Mark Brown
2010-06-03 11:43                         ` Stuart Longland
2010-06-03 11:57                           ` Mark Brown
2010-05-28 12:27               ` Mark Brown
2010-05-29  8:59                 ` Stuart Longland

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=20100528110805.GA9917@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=eric@eukrea.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.