From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751079AbdAMSU1 (ORCPT ); Fri, 13 Jan 2017 13:20:27 -0500 Received: from muru.com ([72.249.23.125]:57446 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750835AbdAMSUZ (ORCPT ); Fri, 13 Jan 2017 13:20:25 -0500 Date: Fri, 13 Jan 2017 10:20:21 -0800 From: Tony Lindgren To: Vignesh R Cc: Greg Kroah-Hartman , Jiri Slaby , Peter Hurley , Sebastian Andrzej Siewior , linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org Subject: Re: [PATCH 0/3] tty: serial: 8250_omap: Enable DMA support Message-ID: <20170113182021.GD2630@atomide.com> References: <20170113080201.6515-1-vigneshr@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170113080201.6515-1-vigneshr@ti.com> User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Vignesh R [170113 00:03]: > This patch series re enables DMA support for UART 8250_omap driver. > > Tested on AM335x, AM437x that use EDMA and OMAP5 and DRA74 EVM with > SDMA. Is 8250_omap serial console working for you on omap5 in general? I've noticed that it's really unresponsive for me as if the FIFO interrupt was not working. For example logging in might take several attempts and a long time with each character showing up much later after some timeout. TX on the uart on omap5 seems to work OK, I do see all the console messages fine. And these patches do not make the issue better or worse. Regards, Tony