From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932091AbcGBLxW (ORCPT ); Sat, 2 Jul 2016 07:53:22 -0400 Received: from basicbox7.server-home.net ([195.137.212.29]:60890 "EHLO basicbox7.server-home.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752142AbcGBLxV (ORCPT ); Sat, 2 Jul 2016 07:53:21 -0400 Subject: Re: [RFC RESEND] serial: 8250: fix regression in 8250 uart driver To: Andy Shevchenko , dinh.linux@anniebear.net References: <575F7325.3030907@kernel.org> <1465897220.30123.26.camel@linux.intel.com> <1465920046.30123.83.camel@linux.intel.com> Cc: Dinh Nguyen , heikki.krogerus@linux.intel.com, peter@hurleysoftware.com, Greg Kroah-Hartman , linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org From: Thorsten Leemhuis Message-ID: Date: Sat, 2 Jul 2016 13:53:17 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <1465920046.30123.83.camel@linux.intel.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? 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. CU, Thorsten