From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932116AbcGBRUG (ORCPT ); Sat, 2 Jul 2016 13:20:06 -0400 Received: from mga03.intel.com ([134.134.136.65]:28313 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752544AbcGBRUE (ORCPT ); Sat, 2 Jul 2016 13:20:04 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,564,1459839600"; d="scan'208";a="839255756" Date: Sat, 2 Jul 2016 22:57:05 +0530 From: Vinod Koul To: Nandor Han Cc: =Dan Williams , Greg Kroah-Hartman , Jiri Slaby , dmaengine@vger.kernel.org, linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: EXT: Re: [PATCH RFC 1/4] dma: imx-sdma - reduce transfer latency for DMA cyclic clients Message-ID: <20160702172704.GV14945@localhost> References: <0ed1e0027f135e9c88d7ac094ca807c7dc8f6713.1465456639.git.nandor.han@ge.com> <20160628143426.GB14945@localhost> <57768552.6060407@ge.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57768552.6060407@ge.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 01, 2016 at 05:59:30PM +0300, Nandor Han wrote: > > > On 28/06/16 17:34, Vinod Koul wrote: > >On Thu, Jun 09, 2016 at 03:16:30PM +0300, Nandor Han wrote: > >>Having the SDMA driver use a tasklet for running the clients > >>callback introduce some issues: > >> - probability to have desynchronized data because of the > >> race condition created since the DMA transaction status > >> is retrieved only when the callback is executed, leaving > >> plenty of time for transaction status to get altered. > >> - inter-transfer latency which can leave channels idle. > >> > >>Move the callback execution, for cyclic channels, to SDMA > >>interrupt (as advised in `Documentation/dmaengine/provider.txt`) > >>to (a)reduce the inter-transfer latency and (b) eliminate the > >>race condition possibility where DMA transaction status might > >>be changed by the time is read. > >> > >>The responsibility of the SDMA interrupt latency > >>is moved to the SDMA clients which case by case should defer > >>the work to bottom-halves when needed. > > > >Both of these look fine. Please change the patch titles to dmaengine: xxxx > > > >Are these going to be merged thru dmaengine tree or serial one? > > > > I will send soon a V2 where I will fix the titles. If you are OK > with all the patchset it can be merged to dmaengine tree, otherwise > probably goes to serial one. Sure I can merge all.. provided ACKs on other patches. -- ~Vinod