From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lars-Peter Clausen Subject: Re: [alsa-devel] [PATCH 20/30] ASoC: samsung: convert to dmaengine API Date: Fri, 12 Apr 2013 21:27:27 +0200 Message-ID: <5168601F.2070409@metafoo.de> References: <1365638712-1028578-1-git-send-email-arnd@arndb.de> <1365638712-1028578-21-git-send-email-arnd@arndb.de> <20130411142706.GB24971@opensource.wolfsonmicro.com> <201304111647.17796.arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201304111647.17796.arnd@arndb.de> Sender: linux-samsung-soc-owner@vger.kernel.org To: Arnd Bergmann Cc: Mark Brown , alsa-devel@alsa-project.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org, Liam Girdwood , Kukjin Kim , linux-arm-kernel@lists.infradead.org List-Id: alsa-devel@alsa-project.org On 04/11/2013 04:47 PM, Arnd Bergmann wrote: > On Thursday 11 April 2013, Mark Brown wrote: >> >> On Thu, Apr 11, 2013 at 02:05:02AM +0200, Arnd Bergmann wrote: >>> In order to build the exynos kernel with CONFIG_ARCH_MULTIPLATFORM, >>> we must convert all users of the Samsung private DMA interface to >>> the generic dmaengine API. This version of the patch adds the >>> generic dmaengine API as an alternative to the existing samsung >>> specific one. Once all the older platforms provide support for >>> the common dmaengine interfaces, we can remove the old code. >> >> There's generic ASoC dmaengine code which should be used instead of open >> coding this. Lars-Peter Clausen and Lee Jones have been working on >> making this a totally generic driver, right now it's a library. > > Ok, I see. I'll drop this patch from my series then and will let someone > else handle this driver in 3.11. We can probably live without sound support > in 3.10 when running a multiplatform kernel, and it will keep working > for exynos-only kernels without the patch. I actually had a look at how the Samsung PCM driver a couple of days back, but I didn't fully grasp how things work with the secondary TX channel for the i2s driver and to make it work with the generic dmaengine PCM driver. The code handling this in the i2s driver seems to be rather messy with lots of ifs and elses. Also things would have would be a lot easier if the dt bindings had used two subnodes each with their own 'dmas' property. - Lars From mboxrd@z Thu Jan 1 00:00:00 1970 From: lars@metafoo.de (Lars-Peter Clausen) Date: Fri, 12 Apr 2013 21:27:27 +0200 Subject: [alsa-devel] [PATCH 20/30] ASoC: samsung: convert to dmaengine API In-Reply-To: <201304111647.17796.arnd@arndb.de> References: <1365638712-1028578-1-git-send-email-arnd@arndb.de> <1365638712-1028578-21-git-send-email-arnd@arndb.de> <20130411142706.GB24971@opensource.wolfsonmicro.com> <201304111647.17796.arnd@arndb.de> Message-ID: <5168601F.2070409@metafoo.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 04/11/2013 04:47 PM, Arnd Bergmann wrote: > On Thursday 11 April 2013, Mark Brown wrote: >> >> On Thu, Apr 11, 2013 at 02:05:02AM +0200, Arnd Bergmann wrote: >>> In order to build the exynos kernel with CONFIG_ARCH_MULTIPLATFORM, >>> we must convert all users of the Samsung private DMA interface to >>> the generic dmaengine API. This version of the patch adds the >>> generic dmaengine API as an alternative to the existing samsung >>> specific one. Once all the older platforms provide support for >>> the common dmaengine interfaces, we can remove the old code. >> >> There's generic ASoC dmaengine code which should be used instead of open >> coding this. Lars-Peter Clausen and Lee Jones have been working on >> making this a totally generic driver, right now it's a library. > > Ok, I see. I'll drop this patch from my series then and will let someone > else handle this driver in 3.11. We can probably live without sound support > in 3.10 when running a multiplatform kernel, and it will keep working > for exynos-only kernels without the patch. I actually had a look at how the Samsung PCM driver a couple of days back, but I didn't fully grasp how things work with the secondary TX channel for the i2s driver and to make it work with the generic dmaengine PCM driver. The code handling this in the i2s driver seems to be rather messy with lots of ifs and elses. Also things would have would be a lot easier if the dt bindings had used two subnodes each with their own 'dmas' property. - Lars