From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754032AbaH2QMd (ORCPT ); Fri, 29 Aug 2014 12:12:33 -0400 Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:21924 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753818AbaH2QM3 (ORCPT ); Fri, 29 Aug 2014 12:12:29 -0400 X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 99.127.230.128 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/pq3P9ujPNhy24kvIFeqZD Date: Fri, 29 Aug 2014 09:12:22 -0700 From: Tony Lindgren To: Sebastian Andrzej Siewior Cc: balbi@ti.com, linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Vinod Koul , Greg Kroah-Hartman , Paul Walmsley Subject: Re: [PATCH 15/15] tty: serial: 8250: omap: add dma support Message-ID: <20140829161221.GO16006@atomide.com> References: <20140815210211.GD9239@atomide.com> <53F5AF0D.5060409@linutronix.de> <20140821184416.GF10066@atomide.com> <53FE3779.5090908@linutronix.de> <20140827202313.GF16006@atomide.com> <20140828082348.GA5413@linutronix.de> <20140828164645.GG16006@atomide.com> <53FF84DF.7080406@linutronix.de> <20140828225454.GM16006@atomide.com> <540048B4.7010807@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <540048B4.7010807@linutronix.de> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Sebastian Andrzej Siewior [140829 02:32]: > On 08/29/2014 12:54 AM, Tony Lindgren wrote: > > OK thanks, I'm seeing the same issue as you. And the idlest registers > > don't show any blockers. Looking at the errata docs, seems like > > "Usage Note 2.7" in sprz318f.pdf says: > > > > Details When configured for DMA operations using smartidle mode (SYSC[4:3].IDLEMODE = > > 0x2), the UART module will not acknowledge incoming idle requests. As a consequence, > > it can prevent L4 from going to idle. > > When there are additional expected transfers, the UART should be placed in force-idle > > mode. > > Ehm. So I haven't found an errata document for omap3630, there is > nothing like that in that one I have for am335x or dra7. The document > you mentioned is for AM3715. Interesting… Yes I would not be suprised if that same bug is in all of them though.. > > So I've added also Paul to Cc, he may have better suggestions for the > > hwmod flags to use. The experimental patch below seems to allow idling > > for me, care to give it a try? > > Yep, this one works. And I see DMA transfers (for RX side) after the > core hit idle so it seems to look good :) OK great :) Looks like the paste bug is there for sure, doing off idle and pasting 240 characters to the console can hang the UART RX after few attempts, and pasting 16 charactes won't show up at all if the system is idling. So you may want to play with that too a bit :) Regards, Tony