Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762634Ab3ECN53 (ORCPT ); Fri, 3 May 2013 09:57:29 -0400 Received: from mail-ie0-f178.google.com ([209.85.223.178]:45899 "EHLO mail-ie0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762307Ab3ECN52 (ORCPT ); Fri, 3 May 2013 09:57:28 -0400 MIME-Version: 1.0 In-Reply-To: <20130502083849.GH25256@gmail.com> References: <1366279934-30761-1-git-send-email-lee.jones@linaro.org> <1366279934-30761-13-git-send-email-lee.jones@linaro.org> <20130501144213.GG25256@gmail.com> <20130502083849.GH25256@gmail.com> Date: Fri, 3 May 2013 15:57:27 +0200 Message-ID: Subject: Re: [PATCH 12/32] ARM: ux500: Remove superfluous 'psize' attribute from Audio platform data From: Linus Walleij To: Lee Jones Cc: "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Arnd Bergmann , Linus WALLEIJ Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2026 Lines: 47 On Thu, May 2, 2013 at 10:38 AM, Lee Jones wrote: >> > 'psize' is used to calculate the maximum DMA burst size. However it >> > is only taken into consideration when editing the DMA channel's >> > configuration. The Audio DMA platform data is only used to allocate >> > a channel, not configure it. That will be done at a later date within >> > the MSP driver. >> > >> > We're also removing comments which are no longer required, as >> > 'data_width' is no longer set in any device's platform data period. >> > >> > Signed-off-by: Lee Jones >> Linus Walleij wrote: >> So if I understand correctly this is now handled by dmaengine_pcm.c, >> os that right? > > Unfortunately not. At the moment ux500 sound is very broken in > Mainline. I looked at it recently and the driver is almost completely > different to the one maintained internally. I was more thinking that the dmaengine_pcm.c which appears to have its functions called from the ux500 ASoC driver should do the calls to slave config to set up proper DMA characteristics for the channel. Maybe that part is in the MSP driver as you say, is that so? > There were DMA changes relating to this driver pending for v3.10, > which I believe have just been taking into -next. I will straighten > out the DMA issues shortly, but there are other ones remaining still - > mostly surrounding widgets. Ideally this is something Ola should fix, > as he has the expertise to do so, but he doesn't appear to have been > very active upstream of late. IIRC there are also patches from Fabio to this stuff so I'm a bit confused, but if the intention is to merge this through ASoC with some other stuff, by all means: Acked-by: Linus Walleij Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/