linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: javier.martin@vista-silicon.com (javier Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH V2] Add i.MX sound support
Date: Mon, 30 Nov 2009 14:13:47 +0100	[thread overview]
Message-ID: <eedb5540911300513j3730078v1393b9b42dca497b@mail.gmail.com> (raw)
In-Reply-To: <20091130124305.GQ27548@pengutronix.de>

2009/11/30 Sascha Hauer <s.hauer@pengutronix.de>

> On Mon, Nov 30, 2009 at 11:43:23AM +0100, javier Martin wrote:
> > Hi Sascha,
> > have you tested capture direction on an i.MX27 based board?
> >
> > I have been testing your patches in the place you suggested and playback
> > seems to work fine but I have several problems with capture stream. I
> found
> > a BUG in the audmux_v1 code
> > and I have fixed it but I am still having problems with capture. The file
> > keeps empty and nothing is recorded.
>
> Capture works fine on my boards.
>
>
>
> > Please could you try the following on an i.MX27 based board?
> >
> > arecord -t raw -c 1 -f S16_LE test.wav
>
> Does it work with two channels? Do you use DMA or FIQ? Could you try the
> other variant?
>

 Unfortunately, I can't test it using two channels because our board has a
wm8974 mono codec. Please could you point me how can I change between FIQ
and DMA? I thought FIQ was only for AC97,

It helped me a lot during development to use a tool like memedit
> (http://www.pengutronix.de/software/memedit/index_en.html) to show a
> register dump of the SSI/Audmux units of a working setup and a non
> working setup. Usually the differences showed quite fast why one was
> working and the other was not.
>

 Indeed, this will be my next step.

 Thank you for the tip.


-- 
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091130/f71483c3/attachment-0001.htm>

  reply	other threads:[~2009-11-30 13:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 15:41 [PATCH V2] Add i.MX sound support Sascha Hauer
2009-11-25 15:41 ` [PATCH 1/3] ASoC: Add a new imx-ssi sound driver Sascha Hauer
2009-11-25 15:41   ` [PATCH 2/3] ASoC: add phycore-ac97 sound support Sascha Hauer
2009-11-25 15:41     ` [PATCH 3/3] ASoC i.MX: remove old i.MX driver Sascha Hauer
2009-11-25 15:53       ` Mark Brown
2009-11-25 15:43     ` [PATCH 2/3] ASoC: add phycore-ac97 sound support Mark Brown
2009-11-25 15:58   ` [PATCH 1/3] ASoC: Add a new imx-ssi sound driver Mark Brown
2009-11-30 16:40     ` javier Martin
2009-11-30 17:09       ` javier Martin
2009-12-01 15:49         ` Sascha Hauer
2009-12-18 14:18           ` javier Martin
2010-01-08 16:18             ` [alsa-devel] " Mark Brown
2009-11-26 15:53 ` [alsa-devel] [PATCH V2] Add i.MX sound support javier Martin
2009-11-26 16:05   ` Mark Brown
2009-11-27  7:58   ` Sascha Hauer
2009-11-27  9:01     ` javier Martin
2009-11-27  9:54       ` Sascha Hauer
2009-11-30 10:43         ` javier Martin
2009-11-30 12:43           ` Sascha Hauer
2009-11-30 13:13             ` javier Martin [this message]
2009-11-30 13:19               ` Sascha Hauer

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=eedb5540911300513j3730078v1393b9b42dca497b@mail.gmail.com \
    --to=javier.martin@vista-silicon.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).