Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: ALSA-devel <alsa-devel@alsa-project.org>,
	Timur Tabi <timur@freescale.com>
Subject: Re: ASoC v2 on PowerPC
Date: Fri, 05 Oct 2007 12:07:57 +0100	[thread overview]
Message-ID: <1191582477.12060.243.camel@localhost.localdomain> (raw)
In-Reply-To: <9e4733910710041012vb8e2a25w7a3b2cc7be80426d@mail.gmail.com>

On Thu, 2007-10-04 at 13:12 -0400, Jon Smirl wrote:
> I'm looking into write a ASoC v2 driver for the Efika. Efika uses a
> Freescale MPC5200B and a STAC9766. This is a practice driver before
> writing one for our target hardware (which doesn't work yet, same CPU
> but different codec).
> 
> I've brought the changes from wolfson/asoc-v2-dev into my powerpc tree
> and got a couple of config errors with ARCH=powerpc.
> 
> sound/soc/pxa/Kconfig:23:warning: 'select' used by config symbol
> 'SND_PXA2XX_SOC_SSP' refers to undefined symbol 'PXA_SSP'
> sound/soc/au1x/Kconfig:35:warning: 'select' used by config symbol
> 'SND_SOC_EXM1200_SSI' refers to undefined symbol 'SND_SOC_CS4251X'
> 

Thanks, I'll fix this.

> Suggestions on the best way to start? Target hardware also has a WM8804 on it.
> 

A good place to start would be looking at the other supported
architectures and codecs and see what fits in best with your target SoC
CPU. Fwiw, Timur Tabi has some working PPC code, although I'm not sure
if it will work on Efika.

I usually start with the I2S driver and the codec in slave mode. Then
move onto the DMA when I see the I2S bits toggling correctly. After the
DMA is up and running I can complete the codec and I2S drivers.

Liam

  reply	other threads:[~2007-10-05 11:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04 17:12 ASoC v2 on PowerPC Jon Smirl
2007-10-05 11:07 ` Liam Girdwood [this message]
2007-10-05 12:55   ` Jon Smirl
2007-10-05 14:03     ` Timur Tabi
2007-10-05 15:26       ` Jon Smirl
2007-10-05 15:30         ` Timur Tabi

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=1191582477.12060.243.camel@localhost.localdomain \
    --to=lg@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jonsmirl@gmail.com \
    --cc=timur@freescale.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