From mboxrd@z Thu Jan 1 00:00:00 1970 From: "George G. Davis" Subject: Re: [alsa-devel] [PATCH] ASoC: Add support for OMAP3 EVM Date: Wed, 25 Feb 2009 15:25:59 -0500 Message-ID: <20090225202559.GO4368@mvista.com> References: <1227591577-23414-1-git-send-email-anuj.aggarwal@ti.com> <20081125132120.1d740c04.jarkko.nikula@nokia.com> <20081125145257.GD12414@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20081125145257.GD12414@sirena.org.uk> Sender: linux-omap-owner@vger.kernel.org To: Mark Brown Cc: Jarkko Nikula , ext Anuj Aggarwal , alsa-devel@alsa-project.org, linux-omap@vger.kernel.org, ext Misael Lopez Cruz List-Id: alsa-devel@alsa-project.org 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