All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valentin Longchamp <valentin.longchamp@epfl.ch>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: alsa-devel@alsa-project.org,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: mx31 snd and mc13783 codec status
Date: Tue, 30 Mar 2010 18:23:18 +0200	[thread overview]
Message-ID: <4BB22576.1070108@epfl.ch> (raw)

Hi Sascha,

For one of our experiments where our robots need to produce sound, I 
would need a sound driver for mx31moboard platform.

I have quickly hacked something based on what you had done for pcm037 
with the MC13783 codec in some of your first sound patches. I know that 
this is not ready for mainline and I'm still struggling to debug my 
code, but I would like to have results quite soon so that my colleague 
could see what sounds (especially regarding to the volume) our system is 
capable to produce.

I would like to know if by any chance you have some updates on this code 
? And do you know if your initial mc13783 codec support coupled with 
mx31 had some limitations ? Our setup is quite straightforward, we have 
direct connection from the mx31 to the mc13783 on a single SSI.

Thanks for your precisions.

Val

-- 
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp@epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEB3494, Station 9, CH-1015 Lausanne

WARNING: multiple messages have this Message-ID (diff)
From: valentin.longchamp@epfl.ch (Valentin Longchamp)
To: linux-arm-kernel@lists.infradead.org
Subject: mx31 snd and mc13783 codec status
Date: Tue, 30 Mar 2010 18:23:18 +0200	[thread overview]
Message-ID: <4BB22576.1070108@epfl.ch> (raw)

Hi Sascha,

For one of our experiments where our robots need to produce sound, I 
would need a sound driver for mx31moboard platform.

I have quickly hacked something based on what you had done for pcm037 
with the MC13783 codec in some of your first sound patches. I know that 
this is not ready for mainline and I'm still struggling to debug my 
code, but I would like to have results quite soon so that my colleague 
could see what sounds (especially regarding to the volume) our system is 
capable to produce.

I would like to know if by any chance you have some updates on this code 
? And do you know if your initial mc13783 codec support coupled with 
mx31 had some limitations ? Our setup is quite straightforward, we have 
direct connection from the mx31 to the mc13783 on a single SSI.

Thanks for your precisions.

Val

-- 
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp at epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEB3494, Station 9, CH-1015 Lausanne

             reply	other threads:[~2010-03-30 16:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 16:23 Valentin Longchamp [this message]
2010-03-30 16:23 ` mx31 snd and mc13783 codec status Valentin Longchamp
2010-03-30 20:40 ` Mark Brown
2010-03-30 20:40   ` Mark Brown
2010-03-31  8:38   ` Sascha Hauer
2010-03-31  8:38     ` Sascha Hauer
2010-03-31  8:34 ` Sascha Hauer
2010-03-31  8:34   ` Sascha Hauer
2010-04-01 16:01   ` Valentin Longchamp
2010-04-01 16:01     ` Valentin Longchamp
2010-04-02  9:53     ` Sascha Hauer
2010-04-02  9:53       ` Sascha Hauer
2010-04-02 10:42       ` Mark Brown
2010-04-02 10:42         ` Mark Brown
2010-04-06 16:00         ` Valentin Longchamp
2010-04-06 16:00           ` Valentin Longchamp
2010-04-07 11:03         ` Sascha Hauer
2010-04-07 11:03           ` Sascha Hauer
2010-04-07 12:12           ` Mark Brown
2010-04-07 12:12             ` 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=4BB22576.1070108@epfl.ch \
    --to=valentin.longchamp@epfl.ch \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.