From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: ext Mark Brown <broonie@sirena.org.uk>
Cc: "George G. Davis" <gdavis@mvista.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
stanley.miao@windriver.com,
ext Anuj Aggarwal <anuj.aggarwal@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
ext Misael Lopez Cruz <mesak82@gmail.com>
Subject: Re: [PATCH] ASoC: Add support for OMAP3 EVM
Date: Thu, 26 Feb 2009 09:18:19 +0200 [thread overview]
Message-ID: <20090226091819.bd509ade.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <20090225202744.GG31637@sirena.org.uk>
On Wed, 25 Feb 2009 21:27:44 +0100
ext Mark Brown <broonie@sirena.org.uk> wrote:
> On Wed, Feb 25, 2009 at 03:25:59PM -0500, George G. Davis wrote:
>
> > Is someone working on updating ASoC drivers for OMAP TWL4030 based
> > boards as recommended above? Just curious since I already made the
> > mistake of creating my own OMAP3 EVM ASoC driver w/o checking the
> > list first. : /
>
> Not to my knowledge.
Stanley Miao started to do some early development on this:
http://mailman.alsa-project.org/pipermail/alsa-devel/2008-November/012946.html
http://mailman.alsa-project.org/pipermail/alsa-devel/2008-November/012995.html
IRCC this work was let to aside to develop since there were some slight
differencies between the boards and also TWL4030 didn't contain all the
features. Stanley, do you remember better?
Probably now there is a better change after tons of generic TWL4030
patches and TWL4030 codec updates from Peter Ujfalusi.
Jarkko
next prev parent reply other threads:[~2009-02-26 7:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 5:39 [PATCH] ASoC: Add support for OMAP3 EVM Anuj Aggarwal
2008-11-25 11:21 ` Jarkko Nikula
2008-11-25 14:52 ` Mark Brown
2009-02-25 20:25 ` [alsa-devel] " George G. Davis
2009-02-25 20:27 ` Mark Brown
2009-02-26 7:18 ` Jarkko Nikula [this message]
2009-02-26 7:36 ` Peter Ujfalusi
-- strict thread matches above, loose matches on Subject: below --
2008-11-21 12:11 Anuj Aggarwal
2008-11-21 16:33 ` David Brownell
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=20090226091819.bd509ade.jarkko.nikula@nokia.com \
--to=jarkko.nikula@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=broonie@sirena.org.uk \
--cc=gdavis@mvista.com \
--cc=linux-omap@vger.kernel.org \
--cc=mesak82@gmail.com \
--cc=stanley.miao@windriver.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