Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3238445imu; Sat, 24 Nov 2018 00:49:07 -0800 (PST) X-Google-Smtp-Source: AJdET5fa/b6LP/A/tRzuTTA87YERnDdCjGteOwYaJ+6eSbiTMFWMHA3r4XBE7mXrddQRvF07LIBZ X-Received: by 2002:a62:31c2:: with SMTP id x185-v6mr19453017pfx.39.1543049347918; Sat, 24 Nov 2018 00:49:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543049347; cv=none; d=google.com; s=arc-20160816; b=GnvxYuK4ohxpnhud+83nFkSy2rxFXOcHddjFSEVU/N3esC05Pbw9OupGAgqqQqC0zU PGQPikVqTtyLywsaLC4I8xI/wYUJgERWBOWFYV1lkQXRF61rcuBlrgQeeViChsB4OOwE 8Zqr+SuHQqSQ1wRc0/JurBZ9k92xrISpKlH4PfK6vm1pf1a0Ig/Q/SmME386TIVSPK1v L0AF6R8dyj9RnNqqWOF4APOjaKQ4WghrblX/SDRvmwlwPFEwsA3NzZS6WSPyT7CLY+P8 klJiHnKAkh/CcBl89MWPN6RC/UYzyHv0FRqgCNVSm312pQ2OqanYX55J+wzWk52j+RcH yjNQ== 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=Qk1ltX6mkUwlBNwb2IRfSBlVmPSSSymaQroF8+xBKxM=; b=TYlCZ9AnJk+K6jf5Zj92BL1bbNxiy+tU31qDUbDpWFLJZvo/Ai9A/d9j+WtWcrromy cMVWDmHMI1pe/osXon3gimTOJdq7aDY2dOpMX9vJPIdlllWBmdth73HKtWWL0KM1XUkR JC/lukhrlUb1X77XTq/vbuE7Kf0t8FK1Qzu+3eBUbctiTRNSMOHU4olW22g2WiKHztLj lInaQc6W18QsryxYRbbwMvDYHsvtaPNbYcVcK+KhWsblWdogeFBVx1WD4u17PliHPfSH WhA3wColXire5nzC34yoJXfYe30UO36VAc71BsgKwGFmiZUB32BOCxF+DRCptUWfp8st dTBQ== 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 e35si25855824pgb.548.2018.11.24.00.48.53; Sat, 24 Nov 2018 00:49:07 -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 S2437179AbeKXFnu (ORCPT + 99 others); Sat, 24 Nov 2018 00:43:50 -0500 Received: from emh07.mail.saunalahti.fi ([62.142.5.117]:47232 "EHLO emh07.mail.saunalahti.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731650AbeKXFnu (ORCPT ); Sat, 24 Nov 2018 00:43:50 -0500 Received: from darkstar.musicnaut.iki.fi (85-76-84-147-nat.elisa-mobile.fi [85.76.84.147]) by emh07.mail.saunalahti.fi (Postfix) with ESMTP id 7595DB0089; Fri, 23 Nov 2018 20:52:15 +0200 (EET) Date: Fri, 23 Nov 2018 20:52:15 +0200 From: Aaro Koskinen To: Peter Ujfalusi Cc: Russell King - ARM Linux , 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: <20181123185215.GH12912@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> <6ed280af-edb6-4be7-82f4-7fc00378103e@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6ed280af-edb6-4be7-82f4-7fc00378103e@ti.com> 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 Hi, On Fri, Nov 23, 2018 at 02:35:04PM +0200, Peter Ujfalusi wrote: > On 22/11/2018 17.12, Russell King - ARM Linux wrote: > > I'm also not sure about this: > > > > if (cpu_is_omap15xx()) > > end++; > > > > in dma_dest_len() - is that missing from the omap-dma driver? It looks > > like a work-around for some problem on OMAP15xx, but I can't make sense > > about why it's in the UDC driver rather than the legacy DMA driver. > > afaik no other legacy drivers were doing similar thing, this must be > something which is needed for the omap_udc driver to fix up something? Here's the patch that added it: https://marc.info/?l=linux-omap&m=119634396324221&w=2 "Make DMA-OUT behave on the 1510 ... the 1510 CPC register was just off-by-one with respect to the 1611 CDAC" A.