From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752602AbcHLK7v (ORCPT ); Fri, 12 Aug 2016 06:59:51 -0400 Received: from mga03.intel.com ([134.134.136.65]:24009 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751636AbcHLK7t (ORCPT ); Fri, 12 Aug 2016 06:59:49 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,510,1464678000"; d="scan'208";a="747786348" Message-ID: <1470999584.4887.94.camel@linux.intel.com> Subject: Re: Wrong "nollp" DW DMAC parameter value on ARC SDP. From: Andy Shevchenko To: Eugeniy Paltsev , "dmaengine@vger.kernel.org" Cc: "linux-kernel@vger.kernel.org" , Nelson Pereira , "viresh.kumar@linaro.org" , "vinod.koul@intel.com" , "linux-snps-arc@lists.infradead.org" Date: Fri, 12 Aug 2016 13:59:44 +0300 In-Reply-To: <1470988994.21247.33.camel@synopsys.com> References: <1470988994.21247.33.camel@synopsys.com> Organization: Intel Finland Oy Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.4-1+b1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2016-08-12 at 08:03 +0000, Eugeniy Paltsev wrote: > Hi, > > "nollp" parameter defines if DW DMAC channel supports multi block > transfer or not. > > It is calculated in runtime, but differently depending on on > availability of pdata. If pdata is absent "nollp" is calculated using > autoconfig hardware registers. Otherwise "nollp" is calculated using > the next code construction: > channel_writel(dwc, LLP, DWC_LLP_LOC(0xffffffff)); > dwc->nollp = DWC_LLP_LOC(channel_readl(dwc, LLP)) == 0; > channel_writel(dwc, LLP, 0); > > I realized that these methods give different results. > For example on ARC AXS101 SDP in case of using autoconfig "nollp" was > calculated as "true" (and DMAC works fine),  > otherwise "nollp" was calculated as "false" (and DMAC doesn't work). Can you show out what the value you read back? > > So I'm wondering how the code in question really works? > From DW AHB DMAC databook I wasn't able to find anything relevant to > this tricky implementation. Could you please clarify a little but what > happens here? "Table 4-1: ... Hardcode Channel x LLP register to 0? ... Description: If set to 1, hardcodes channel x Linked List Pointer register to 0 (LLPx.LOC == 0), ..." > Maybe we should add "nollp" field in pdata structure and receive it > from pdata/device tree (like we use "is_private" or "is_memcpu" > fields) Yeah, perhaps we can remove that trick since we need this flag to be set on Intel Quark which might have the same issue as your case [1]. [1] http://www.spinics.net/lists/linux-serial/msg22948.html -- Andy Shevchenko Intel Finland Oy