alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Brian Austin <brian.austin@cirrus.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, heelrod@gmail.com, lrg@slimlogic.co.uk
Subject: Re: [PATCH] ASoC: Add support for Cirrus Logic CS42L52 LowpowerStereo Codec
Date: Fri, 26 Feb 2010 11:18:00 -0600	[thread overview]
Message-ID: <1267204680.13721.105.camel@heelrod.ad.cirrus.com> (raw)
In-Reply-To: <20100226101259.GA18053@rakim.wolfsonmicro.main>

On Fri, 2010-02-26 at 10:12 +0000, Mark Brown wrote:
> On Thu, Feb 25, 2010 at 07:59:29PM -0600, Austin, Brian wrote:
> 
> > Thanks alot for the feedback, I'll start fixing it up tomorrow.
> > Should I send the smdk2443 driver, or wait till this is fixed up?
> 
> May as well send it, there should be relatively little coupling to the
> CODEC driver.  Is this a plugin module for the SMDK or does it need
> flying wires or mods to get it hooked up?
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 

It requires wiring onto the I2C Connector and Dropping lines on the I2S
as well.

The device is wired correctly, just haven't gotten it to work with the
newer kernels.

  reply	other threads:[~2010-02-26 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1267142855-12854-1-git-send-email-brian.austin@cirrus.com>
2010-02-26  0:53 ` [PATCH] ASoC: Add support for Cirrus Logic CS42L52 Lowpower Stereo Codec Mark Brown
2010-02-26  1:59   ` [PATCH] ASoC: Add support for Cirrus Logic CS42L52 LowpowerStereo Codec Austin, Brian
2010-02-26 10:12     ` Mark Brown
2010-02-26 17:18       ` Brian Austin [this message]
2010-02-26 21:28         ` Mark Brown
2011-06-22  4:41 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=1267204680.13721.105.camel@heelrod.ad.cirrus.com \
    --to=brian.austin@cirrus.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=heelrod@gmail.com \
    --cc=lrg@slimlogic.co.uk \
    /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).