From: philippe.retornaz@epfl.ch (Philippe Rétornaz)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM ASoC: add sound driver for imx27pdk using mc13783 codec
Date: Wed, 25 Jan 2012 16:45:40 +0100 [thread overview]
Message-ID: <2667396.yifGumf5nD@laptop> (raw)
In-Reply-To: <201107271028.09928.philippe.retornaz@epfl.ch>
Hi
> Le vendredi 8 juillet 2011 16:19:22, Lambrecht J?rgen a ?crit :
> > indeed, doesn't work at all. I know it used to work on 2.6.34.
> > We also have a fsl linux 2.6.22 were it works.
> > I must say: when i use aplay to play a mono file, then there is no
> > error, it just never ends, and no sound also.
> > For a stereo file, it gives the error.
> > Mark also that when I use madplay (v0.15.2) (or mp3play) to play a mono
> > or stereo mp3, it allocates 3 DMA channels, but only frees one after the
> > error.
>
> Did you made any progress on this ?
I have a working sound support for the mx31moboard boards available here:
http://github.com/retornaz/linux/commits/moboard-sound
It's basically Sascha mc13783 codec driver (from his git tree) rebased on 3.2
and some mx31moboad specific code.
I can playback & record sound on our board (2 channels at 16Khz) with the sdma.
Sascha, do you have any plan to upstream the mc13783 codec driver ?
Thanks,
Philippe
next prev parent reply other threads:[~2012-01-25 15:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 13:24 [RFC PATCH] ARM ASoC: add sound driver for imx27pdk using mc13783 codec Jürgen Lambrecht
2011-07-08 14:11 ` Philippe Rétornaz
2011-07-08 14:19 ` Lambrecht Jürgen
2011-07-27 8:28 ` Philippe Rétornaz
2011-07-29 19:14 ` Jürgen Lambrecht
2011-09-20 11:39 ` Philippe Rétornaz
2012-01-25 15:45 ` Philippe Rétornaz [this message]
2012-01-28 20:57 ` Fabio Estevam
2012-01-29 19:01 ` Philippe Rétornaz
2012-01-30 15:59 ` Fabio Estevam
2012-02-02 17:32 ` [alsa-devel] " Mark Brown
2012-02-03 7:45 ` Philippe Rétornaz
2012-02-03 11:58 ` Mark Brown
2012-02-09 21:24 ` Fabio Estevam
2011-07-09 2:25 ` Mark Brown
2011-07-11 10:30 ` Lambrecht Jürgen
2011-07-11 11:44 ` Mark 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=2667396.yifGumf5nD@laptop \
--to=philippe.retornaz@epfl.ch \
--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