Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2442075imu; Sat, 22 Dec 2018 23:09:07 -0800 (PST) X-Google-Smtp-Source: AFSGD/XsEHk0ip4HgUTOAt6exyq1T2vxJKplvhnXzbvIc7OHp/RhDXEqP1ONSJ6N5SA1OVIr0nZs X-Received: by 2002:a02:f42:: with SMTP id h63mr5769937jad.133.1545548947792; Sat, 22 Dec 2018 23:09:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545548947; cv=none; d=google.com; s=arc-20160816; b=e3CDsuyn4ygRr79teGfZrOrBhZwyE+DYTIqFka7J6VMh8Ca29TjYWrBfrRJf1H3glE A7tyJBxYHl0H4Vc6FbLeMbYc6IoCrfhmVyYV56T78nkS6GufoqQVFcQATVafWkXX2zYb pSqelA+R4FQhsb96RWHbBJQ09k3FpPNVh9QjpAkJyIKpgGN7Q9pHOGOEiJ49tJMGRaY2 nIFG+BL/Esp9GxgIpYhYqP+UQixuBp4DdqCbcz25PDv+/jM+MuW71egrlQ0U2S7uk/KP EXogPoq7Ysm0sBezB+58pCzHmA1L/O3pij2mhCQAbg7fppdi/MoMXDeZqWvBv5WTD8bC 90tg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=8DpS/HMq0L5ojKcbuC7atSEIzvC49JUzH0eFuyY/Yno=; b=ZC6l807tZfn1tQuMbv+rulSkjkyKGfLFKRN3aVKY7fbA7fKRVz8p3z+T8gMaKTrukv LUrUT81yTJ0e0fywz0AlC/9unWWLHPRi70ufXPg+QXmofVWOvmruXM81e0LwED2W09CI axeCk4WwCDycbuOUKqj1ooekUaALQuBNA0gDg7f9bHtEOgUsGlGHA0u4ZSFQFLYumlnz 8hsRQ1HIQNVOUIL5OTDQHo3NxdlcYfSvAPxHz76B+UQaPtiqD/NPZcRDPXmBCivgZNoz hiiotWyvZCp69D6m7Zt1juQqq4Ru+RyBr6E5vTJi8UoBlKLtZOfSZdf8zzP0vn/+u3ev PxAQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i135si2707298iti.83.2018.12.22.23.08.53; Sat, 22 Dec 2018 23:09:07 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391810AbeLUUgH (ORCPT + 99 others); Fri, 21 Dec 2018 15:36:07 -0500 Received: from mail-out.m-online.net ([212.18.0.9]:58889 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732146AbeLUUgH (ORCPT ); Fri, 21 Dec 2018 15:36:07 -0500 Received: from frontend01.mail.m-online.net (unknown [192.168.8.182]) by mail-out.m-online.net (Postfix) with ESMTP id 43M0l54Cvnz1qvwC; Fri, 21 Dec 2018 21:36:01 +0100 (CET) Received: from localhost (dynscan1.mnet-online.de [192.168.6.70]) by mail.m-online.net (Postfix) with ESMTP id 43M0l50hjwz1qsJh; Fri, 21 Dec 2018 21:36:01 +0100 (CET) X-Virus-Scanned: amavisd-new at mnet-online.de Received: from mail.mnet-online.de ([192.168.8.182]) by localhost (dynscan1.mail.m-online.net [192.168.6.70]) (amavisd-new, port 10024) with ESMTP id PpUddr77N0NU; Fri, 21 Dec 2018 21:35:59 +0100 (CET) X-Auth-Info: T06MoJD12PDo90wuQYGN6QtiOuFp/1X2KFMzFVVBw+k= Received: from [IPv6:::1] (unknown [195.140.253.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.mnet-online.de (Postfix) with ESMTPSA; Fri, 21 Dec 2018 21:35:59 +0100 (CET) Subject: Re: [PATCH] Revert "serial: 8250: Fix clearing FIFOs in RS485 mode again" To: Paul Burton Cc: "linux-serial@vger.kernel.org" , Greg Kroah-Hartman , "linux-kernel@vger.kernel.org" , Paul Burton , Daniel Jedrychowski , "linux-mips@vger.kernel.org" , stable , Ezequiel Garcia References: <20181213174834.kxdy6fphaeoivqgh@pburton-laptop> <20181216200833.27928-1-paul.burton@mips.com> <93a3c76b-f4ba-57ae-9d80-6e945b4f3181@denx.de> <20181216213901.hpll7wqzhqvfgkfy@pburton-laptop> <28a1d4ae-493d-8bbc-46f7-ad41ca04d782@denx.de> <20181216222815.4t4xhaiy6rvfaogq@pburton-laptop> From: Marek Vasut Message-ID: <78839e8c-0278-6060-0dd2-a84a19258a8a@denx.de> Date: Fri, 21 Dec 2018 21:08:28 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20181216222815.4t4xhaiy6rvfaogq@pburton-laptop> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/16/2018 11:28 PM, Paul Burton wrote: > Hi Marek, > > On Sun, Dec 16, 2018 at 11:01:18PM +0100, Marek Vasut wrote: >>>>> I did suggest an alternative approach which would rename >>>>> serial8250_clear_fifos() and split it into 2 variants - one that >>>>> disables FIFOs & one that does not, then use the latter in >>>>> __do_stop_tx_rs485(): >>>>> >>>>> https://lore.kernel.org/lkml/20181213014805.77u5dzydo23cm6fq@pburton-laptop/ >>>>> >>>>> However I have no access to the OMAP3 hardware that Marek's patch was >>>>> attempting to fix & have heard nothing back with regards to him testing >>>>> that approach, so here's a simple revert that fixes the Ingenic JZ4780. >>>>> >>>>> I've marked for stable back to v4.10 presuming that this is how far the >>>>> broken patch may be backported, given that this is where commit >>>>> 2bed8a8e7072 ("Clearing FIFOs in RS485 emulation mode causes subsequent >>>>> transmits to break") that it tried to fix was introduced. >>>> >>>> OK, I tested this on AM335x / OMAP3 and the system is again broken, so >>>> that's a NAK. >>> >>> To be clear - what did you test? This revert or the patch linked to >>> above? >>> >>> This revert would of course reintroduce your RS485 issue because it just >>> undoes your change. >> >> The revert. Which of the two patches do you need me to test. > > The one in the email I sent on Thursday 13th at 01:48:06 UTC, linked to > at lore.kernel.org in the quote right above: > > https://lore.kernel.org/lkml/20181213014805.77u5dzydo23cm6fq@pburton-laptop/ > > You replied with comments on the patch, you just never tested it or > never told me if you did. The lack of response means I don't know > whether that potential patch even still works for your system, hence the > revert. I shared the entire testcase, which now fails on AM335x due to this revert. Is there any progress on a proper fix from your side which does not break the AM335x ? -- Best regards, Marek Vasut