From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH 1/7] [RFC] OMAP: MCBSP: hwmod database for 2xxx devices Date: Fri, 15 Oct 2010 15:24:03 +0100 Message-ID: <20101015142402.GM14782@rakim.wolfsonmicro.main> References: <1286296662-7639-1-git-send-email-kishon@ti.com> <201010061017.13908.peter.ujfalusi@nokia.com> <201010131131.49967.peter.ujfalusi@nokia.com> <20101015095109.2d76babe.jhnikula@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20101015095109.2d76babe.jhnikula@gmail.com> Sender: linux-omap-owner@vger.kernel.org To: Jarkko Nikula Cc: "Varadarajan, Charulatha" , Peter Ujfalusi , "linux-omap@vger.kernel.org" , "alsa-devel@alsa-project.org" , "Kamat, Nishant" , "Datta, Shubhrajyoti" , "Basak, Partha" , "Girdwood, Liam" , "ABRAHAM, KISHON VIJAY" List-Id: alsa-devel@alsa-project.org On Fri, Oct 15, 2010 at 09:51:09AM +0300, Jarkko Nikula wrote: > So things can get complicated if trying to implement generic transfer > API to general purpose block like McBSP compared to some dedicated > block where transfer setup is always more or less the same. I tend to agree. Experience with some of the other platforms suggests that doing the abstracted API for data transfers doesn't save you that much unless the hardware is really hard to manage and so needs lots of code that can be factored out from the leaf drivers.