Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3063152imu; Mon, 17 Dec 2018 12:36:41 -0800 (PST) X-Google-Smtp-Source: AFSGD/V0d32Y4itpS1+n8BrRw1Dxiausga1mZfS77fr/2M1ixkXk/kXNm2IXTn8gETDI5m+QA0RG X-Received: by 2002:a17:902:9047:: with SMTP id w7mr14054743plz.270.1545079001904; Mon, 17 Dec 2018 12:36:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545079001; cv=none; d=google.com; s=arc-20160816; b=i7GyM+QMmf95y6Gy7wFK5VoScOCjtpf3KsroloC9yp+OLWLGpi9tXcepPXQ6k/egMF /ikxVqGdxUNp23suor9M53YZFXThR+y+lmHvinat3KVMKuDrBad0bjMDMBlB4e6r5BPw c7Ad3FcUCMW1Ynn8yiND/VO+jpHHZcF5mKMy/L+CXJyagvnTLXrG366ZW8qKIh1JMO/7 i6HgWBJmDnQZBH1E+labANQb/jyxydb7QIqzNOZqlFTxd2/VRr/ddJVCthZU4CDItjCe UxKswjLOCy5KB3hcEBc7gEgmAndaCI8vUxkp9sb/ueW5DAyad/7HI4qLoXz3qFrAx1/r 6swg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=CFp5QEbedKQOtYqiotCwdH9h6M17A1FfJwL0fiddRZA=; b=wdmURFpoQFI5S9L1H1dP7CnjV/L+/4NQRJRL195FtSQWKkT6JESjBfqNQx4NU37UvO 5xxh8X7DSTVefR1aL1braTR3XpuWJiX5r83iaEFXbQ2//GIZYXlsGBx6kmI6bo57KSnG mVHXMGnEnm/IDIxFjY9bOoBocnrC69sdrjOjQ0MiEo3Jek9tE44XdHZKZdsGQjSleq/6 MzGFYpTIelJc3/4GqucB8+rm6pRxplFmQ3fw82dBpRK95NLSNlxm3kDiXim75lQepC/x IAluatrlveTELMwCqT5ZZ5w0CrdKA/k4la6WTNckKCAdu6QLYFOThOVUe62yoJmtUVEZ x60Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=iki.fi Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k5si11492431plt.111.2018.12.17.12.36.26; Mon, 17 Dec 2018 12:36:41 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=iki.fi Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389261AbeLQTRD (ORCPT + 99 others); Mon, 17 Dec 2018 14:17:03 -0500 Received: from emh04.mail.saunalahti.fi ([62.142.5.110]:49514 "EHLO emh04.mail.saunalahti.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389145AbeLQTRB (ORCPT ); Mon, 17 Dec 2018 14:17:01 -0500 Received: from darkstar.musicnaut.iki.fi (85-76-70-99-nat.elisa-mobile.fi [85.76.70.99]) by emh04.mail.saunalahti.fi (Postfix) with ESMTP id 3CEC930084; Mon, 17 Dec 2018 21:16:58 +0200 (EET) Date: Mon, 17 Dec 2018 21:16:58 +0200 From: Aaro Koskinen To: Russell King - ARM Linux , Peter Ujfalusi Cc: vkoul@kernel.org, dan.j.williams@intel.com, dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org, tony@atomide.com, linux-omap@vger.kernel.org Subject: Re: [PATCH] dmaengine: ti: omap-dma: Configure LCH_TYPE for OMAP1 Message-ID: <20181217191657.GB7288@darkstar.musicnaut.iki.fi> References: <20181119104040.12885-1-peter.ujfalusi@ti.com> <20181119184649.GE16897@darkstar.musicnaut.iki.fi> <6af8c6e7-bf5c-5555-161b-5d3fb7ecae43@ti.com> <20181120210406.GB24888@darkstar.musicnaut.iki.fi> <20181122102948.GN6920@n2100.armlinux.org.uk> <20181122151236.GA9611@n2100.armlinux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181122151236.GA9611@n2100.armlinux.org.uk> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 22, 2018 at 03:12:36PM +0000, Russell King - ARM Linux wrote: > Also we can't deal with the omap_set_dma_dest_burst_mode() setting - > DMAengine always uses a 64 byte burst, but udc wants a smaller burst > setting. Does this matter? Looking at OMAP1 docs, it seems it supports only 16 bytes. Then checking DMAengine code, I don't think these CSDP bit values are not valid for OMAP1: CSDP_SRC_BURST_1 = 0 << 7, CSDP_SRC_BURST_16 = 1 << 7, CSDP_SRC_BURST_32 = 2 << 7, CSDP_SRC_BURST_64 = 3 << 7, From TI SPRU674 document, pages 50-51: 0 single access (no burst) 1 single access (no burst) 2 burst 4 3 reserved (do not use this setting) So if CSDP_SRC_BURST_64 (3) gets programmed OMAP1, I wonder what is the end result, no burst or burst 4... A.