Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Beisert <jbe@pengutronix.de>
To: alsa-devel@alsa-project.org
Cc: Timur Tabi <timur@freescale.com>
Subject: Re: SoC sound support for imx27
Date: Thu, 24 Apr 2008 13:19:39 +0200	[thread overview]
Message-ID: <200804241319.40134.jbe@pengutronix.de> (raw)
In-Reply-To: <1208964986.3286.62.camel@localhost.localdomain>

On Wednesday 23 April 2008 17:36, Liam Girdwood wrote:
> On Wed, 2008-04-23 at 16:54 +0200, Juergen Beisert wrote:
> > Hi,
> >
> > I'm going to adapt Freescale's i.MX27 CPU to the SoC sound support via
> > I2S. I found the imx21 already in the repository (may it will help for my
> > job). Is anybody else working on i.MX27 support (to avoid to reinvention
> > everything)?
>
> It's not fully supported atm. However I've had interest from a few folks
> who are interested in completing support.
>
> Currently working :-
>
>  o i.MX2x SSI is complete (same as i.MX3)

But why there are different files for different CPUs when their hardware "on 
chip" is the same?

> Todo:
>
>  o i.MX2x DMA is not completed. There is a half ASoC ported OSS based
> implementation in git atm, although it's not complete due to my only
> remaining i.MX21 board dying. Should be only about 1 weeks effort to
> complete this.

I have an i.MX27 and i.MX31 board here. Question is, what kind of 
CPU/architecture support you are using for i.MX21? The one from arch/arm/imx? 
Or something from arch/arm/mxc3, arch/arm/plat-mxc?

So now we have a few (nearly working) implementations. What should be used? 
The implementations from soc/imx or from soc/fsl?

Juergen

-- 
Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
    Handelsregister: Amtsgericht Hildesheim, HRA 2686
         Vertretung Sued/Muenchen, Germany
   Phone: +49-8766-939 228 |  Fax: +49-5121-206917-9

  reply	other threads:[~2008-04-24 11:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23 14:54 SoC sound support for imx27 Juergen Beisert
2008-04-23 15:36 ` Liam Girdwood
2008-04-24 11:19   ` Juergen Beisert [this message]
2008-04-24 14:26     ` Liam Girdwood
2008-04-24 14:31       ` Timur Tabi
2008-04-24 14:11   ` Juergen Beisert
2008-04-24 14:30     ` Liam Girdwood
2008-05-05 10:56       ` Juergen Beisert
2008-05-05 12:42         ` Mark Brown
2008-05-05 12:55           ` Juergen Beisert
2008-05-05 13:12             ` Mark Brown
2008-05-08  7:54           ` Juergen Beisert
2008-05-08  9:33             ` Mark Brown
2008-05-08 10:27               ` How are events of headphone plug/unplug handled in ASOC Srinivas.Kandagatla
2008-05-08 10:31                 ` Mark Brown
2008-05-08 11:25             ` SoC sound support for imx27 Liam Girdwood
2008-04-23 15:44 ` 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=200804241319.40134.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=alsa-devel@alsa-project.org \
    --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