From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751600AbdAQXcf (ORCPT <rfc822;w@1wt.eu>);
        Tue, 17 Jan 2017 18:32:35 -0500
Received: from muru.com ([72.249.23.125]:58308 "EHLO muru.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751579AbdAQXbk (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 17 Jan 2017 18:31:40 -0500
Date: Tue, 17 Jan 2017 15:25:37 -0800
From: Tony Lindgren <tony@atomide.com>
To: Vignesh R <vigneshr@ti.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Jiri Slaby <jslaby@suse.com>, Peter Hurley <peter@hurleysoftware.com>,
        Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
        "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/3] tty: serial: 8250_omap: Enable DMA support
Message-ID: <20170117232536.GZ7403@atomide.com>
References: <20170113080201.6515-1-vigneshr@ti.com>
 <20170113182021.GD2630@atomide.com>
 <b27b95a9-40b8-ebef-3457-ce87db6b26e5@ti.com>
 <f978273d-39eb-e5d7-a95e-4a2e4be9e23c@ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f978273d-39eb-e5d7-a95e-4a2e4be9e23c@ti.com>
User-Agent: Mutt/1.7.2 (2016-11-26)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

* Vignesh R <vigneshr@ti.com> [170117 02:06]:
> 
> 
> On Tuesday 17 January 2017 11:36 AM, Vignesh R wrote:
> > 
> > 
> > On Friday 13 January 2017 11:50 PM, Tony Lindgren wrote:
> >> * Vignesh R <vigneshr@ti.com> [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.
> >>
> > 
> > Yes, I did face the same issue on omap5 using 8250_omap driver for
> > console. Looks like this bug has existed all along.
> > 
> 
> This looks a separate issue, I don't see any errata specific errata wrt
> UART on OMAP5. I will try to debug further.

OK maybe it's something configured or not configured by the bootloader
that we're missing in the Linux driver?

Other than the omap5 issue, 8250_OMAP seems to behave on all variants
that I've tried it with so far.

Regards,

Tony