From: "George G. Davis" <gdavis@mvista.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Jarkko Nikula <jarkko.nikula@nokia.com>,
ext Anuj Aggarwal <anuj.aggarwal@ti.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
ext Misael Lopez Cruz <mesak82@gmail.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: Add support for OMAP3 EVM
Date: Wed, 25 Feb 2009 15:25:59 -0500 [thread overview]
Message-ID: <20090225202559.GO4368@mvista.com> (raw)
In-Reply-To: <20081125145257.GD12414@sirena.org.uk>
Hi,
On Tue, Nov 25, 2008 at 02:52:58PM +0000, Mark Brown wrote:
> On Tue, Nov 25, 2008 at 01:21:20PM +0200, Jarkko Nikula wrote:
>
> > Or if those EVM's & SDP's can route TWL4030 audio connections more
> > flexible than Beagle but somewhat similar manner, then probably have one
> > single machine driver for all EVM's?
>
> > Otherwise it doesn't make very much sense to have n similar machine
> > drivers where only functions and variable names differ.
>
> Yes, it looks like a lot of these drivers could be redone along the
> lines of s3c24xx_uda134x.c with platform data specifying the differences
> between the boards.
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. : /
--
Regards,
George
next prev parent reply other threads:[~2009-02-25 20:25 UTC|newest]
Thread overview: 7+ 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 ` George G. Davis [this message]
2009-02-25 20:27 ` [alsa-devel] " Mark Brown
2009-02-26 7:18 ` Jarkko Nikula
2009-02-26 7:36 ` Peter Ujfalusi
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=20090225202559.GO4368@mvista.com \
--to=gdavis@mvista.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=broonie@sirena.org.uk \
--cc=jarkko.nikula@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=mesak82@gmail.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