Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3192074imu; Fri, 23 Nov 2018 23:45:39 -0800 (PST) X-Google-Smtp-Source: AJdET5cOSzAcRtCwC8X/AvUtLr3qyKuuTixuCnO2ylYzkGlhZlCVvnAuUXn40daD1Fc87YuW3Zrs X-Received: by 2002:a62:3241:: with SMTP id y62-v6mr19542828pfy.218.1543045539249; Fri, 23 Nov 2018 23:45:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543045539; cv=none; d=google.com; s=arc-20160816; b=Kn6wqN3J1NB3Q7yzwkP6D6HMJO1vqgXCBymeDWQaTJpF395Mi9eLj7JF5M/+BkYg10 8xPrOBdcYrb/9fCxi/pqqGdVi43LXfArKbv/hsnXx8FvVg3uaoiGezkaxWeNEnYMJQov tEAB2qJVScK9lKFNZrOc4w7MPdkYswpnIyVXa88sBtOODKmYhXL4U0Dci0kuHZSKBW5u gBTYD1NIiBfBsC4oVtbSkidK02cWt7xWY/QtgsV6SjHZ3Moke4O+RSDlUpZTLnC6biPJ TXT4DFxHAECAVrBkjyDwA1DPupY0XNDF2IYZSBbroP3iH2BHHFyVvhlCOQptPJGilY+u id6Q== 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=Jh15muozvesuY2a6jIttVdh+V1XRMqdH+Hc78pWVFoU=; b=zqa3LyxkTezTEJcQjR/9xNt8zSPnYyIQVv82pyniLBmPuYnlVSnprrM1MzzY9J9TS2 QPDyqXvZQ8Vp2Rf1spUxntTXUAwRkeMXQaOkTYsngXv6cLSuEXRUWQkuoEaNjHcbilrY YZy9zeg6YstOxH99nP69kKYOi+mfsRuffuFtoaUsPmaiknOGGbNx1cc9lSIH7rGN7yLU LmV8rVhtizsadd6yKuzaNSz1uabJvfTXNjmnInp/whoUF4a5Gvn4yDh87QvnViF7KKce kgix5CyuCx9JZFyiOjn/X/OOtOfn9RgBGp/04tVALB6GpEdwVDMn9wxpM+1gtRLobJ43 I3Sg== 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 f1si22739504pgq.553.2018.11.23.23.45.25; Fri, 23 Nov 2018 23:45:39 -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 S2438992AbeKWJFy (ORCPT + 99 others); Fri, 23 Nov 2018 04:05:54 -0500 Received: from emh01.mail.saunalahti.fi ([62.142.5.107]:58832 "EHLO emh01.mail.saunalahti.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728441AbeKWJFy (ORCPT ); Fri, 23 Nov 2018 04:05:54 -0500 Received: from darkstar.musicnaut.iki.fi (85-76-84-147-nat.elisa-mobile.fi [85.76.84.147]) by emh01.mail.saunalahti.fi (Postfix) with ESMTP id 08877200F3; Fri, 23 Nov 2018 00:24:26 +0200 (EET) Date: Fri, 23 Nov 2018 00:24:26 +0200 From: Aaro Koskinen To: Russell King - ARM Linux Cc: Peter Ujfalusi , 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: <20181122222426.GC11423@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 Hi, On Thu, Nov 22, 2018 at 03:12:36PM +0000, Russell King - ARM Linux wrote: > On Thu, Nov 22, 2018 at 10:29:48AM +0000, Russell King - ARM Linux wrote: > > On Tue, Nov 20, 2018 at 11:04:06PM +0200, Aaro Koskinen wrote: > > > I had switched to PIO mode in 2015 since the WARNs about legacy DMA > > > API were too annoying and flooding the console. And now that I tried > > > using DMA again with g_ether, it doesn't work anymore. The device get's > > > recognized on host side, but no traffic goes through. Switching back to > > > PIO makes it to work again. > > > > A solution to that would be to do what the warning message says, and > > update the driver to the DMAengine API. Fully agreed, but I was busy debugging other more serious issues, and just wanted to get a reliable ssh or USB serial access to the device without any extra noise, so switching to PIO using a module parameter is probably what most users do in such situations. > Here's a partial conversion (not even build tested) - it only supports > OUT transfers with dmaengine at the moment. Thanks, I'll take a closer look and try to do some testing hopefully during the weekend. A.