From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Valentin Longchamp <valentin.longchamp@epfl.ch>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
alsa-devel@alsa-project.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: mx31 snd and mc13783 codec status
Date: Tue, 30 Mar 2010 21:40:21 +0100 [thread overview]
Message-ID: <20100330204021.GA4666@sirena.org.uk> (raw)
In-Reply-To: <4BB22576.1070108@epfl.ch>
On Tue, Mar 30, 2010 at 06:23:18PM +0200, Valentin Longchamp wrote:
> 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.
If you're struggling to find time to do full support for the CODEC a
good technique is often to get just very basic fixed function support
(say just DAC to headphone support) implemented and merged, then go back
and implement
I'd also suggest looking at the current Freescale BSPs - obviously this
device is used on a lot of Freescale reference boards and I believe
there's a reasonably mainlineish driver in the BSPs they have for
current devices.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: mx31 snd and mc13783 codec status
Date: Tue, 30 Mar 2010 21:40:21 +0100 [thread overview]
Message-ID: <20100330204021.GA4666@sirena.org.uk> (raw)
In-Reply-To: <4BB22576.1070108@epfl.ch>
On Tue, Mar 30, 2010 at 06:23:18PM +0200, Valentin Longchamp wrote:
> 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.
If you're struggling to find time to do full support for the CODEC a
good technique is often to get just very basic fixed function support
(say just DAC to headphone support) implemented and merged, then go back
and implement
I'd also suggest looking at the current Freescale BSPs - obviously this
device is used on a lot of Freescale reference boards and I believe
there's a reasonably mainlineish driver in the BSPs they have for
current devices.
next prev parent reply other threads:[~2010-03-30 20:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 16:23 mx31 snd and mc13783 codec status Valentin Longchamp
2010-03-30 16:23 ` Valentin Longchamp
2010-03-30 20:40 ` Mark Brown [this message]
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=20100330204021.GA4666@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=valentin.longchamp@epfl.ch \
/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.