From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751981AbcGBL7H (ORCPT ); Sat, 2 Jul 2016 07:59:07 -0400 Received: from mga11.intel.com ([192.55.52.93]:36766 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750728AbcGBL7F (ORCPT ); Sat, 2 Jul 2016 07:59:05 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,562,1459839600"; d="scan'208";a="1009450947" Message-ID: <1467460739.30123.443.camel@linux.intel.com> Subject: Re: [RFC RESEND] serial: 8250: fix regression in 8250 uart driver From: Andy Shevchenko To: Thorsten Leemhuis , dinh.linux@anniebear.net Cc: Dinh Nguyen , heikki.krogerus@linux.intel.com, peter@hurleysoftware.com, Greg Kroah-Hartman , linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org Date: Sat, 02 Jul 2016 14:58:59 +0300 In-Reply-To: References: <575F7325.3030907@kernel.org> <1465897220.30123.26.camel@linux.intel.com> <1465920046.30123.83.camel@linux.intel.com> Organization: Intel Finland Oy Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.3-1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2016-07-02 at 13:53 +0200, Thorsten Leemhuis wrote: > On 14.06.2016 18:00, Andy Shevchenko wrote: > > On Tue, 2016-06-14 at 10:27 -0500, dinh.linux@anniebear.net wrote: > > > > On Mon, 2016-06-13 at 21:59 -0500, Dinh Nguyen wrote: > > > > I suppose this one, i.e. commit dd4e91d538b3 ("dmaengine: slave > > > > means at > > > > least one of DMA_SLAVE, DMA_CYCLIC"), solves the issue. > > > Hmm...that commit didn't seem to fix my issue. > > […] > > > Does this mean that the 8250_dw.c driver can no longer use DMA? > > > > It means that previously the use of DMA engine whatever was used is > > not > > correct in your case. There is no issues in UART driver, the issue > > is in > > DMA controller driver. > > > > I'm working on a quirk that will allow user to enforce PIO mode for > > Rx/Tx or both. In that case if DMA controller can't be fixed you > > still > > might use DMA for Tx. > > What's the status of this issue? Apparently I'm not going to fix DMA controller engine if it even would be fixed (I don't know what one you use), but I will continue with the mentioned quirk as soon as I finish one higher priority task. Sorry for a delay. > Just wondering, as this issue is listed > in my regression reports for 4.7 and it seems nothing much happened > for > more than a week now – which is a bad sign as the 4.7 release seems > only > a week or two away. -- Andy Shevchenko Intel Finland Oy