Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp2878238pxu; Sat, 19 Dec 2020 05:06:23 -0800 (PST) X-Google-Smtp-Source: ABdhPJyQdBbm0/SFXAGSV3vUHbSh49NTiZeUa5IscBqhGYGX9IAqhN3WKt54yGCiOhLt4XIbO1Zu X-Received: by 2002:a17:906:1302:: with SMTP id w2mr8564239ejb.413.1608383183382; Sat, 19 Dec 2020 05:06:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1608383183; cv=none; d=google.com; s=arc-20160816; b=bj3RlKZBBud0ztgMl5i44XDqMI5TUKZ8vapFbsMAYBa3bt4+Xr8VJBg932qUSZG1Q1 a10h0ZaPsh8s5E7eFMx7YA2qtV2k+GoHg2CUYq/cX/iC32Ish4840xiLT4g93j86Px4f qXp/0BBsZr44C0xq4flVvGE8XjsC3XdZeFLerfOmRxU4ZoDlzmerwgby+LTienjQ33rO arJLis8icHSlEKG1WOVIQXscj4okfgWZSg/nZtFHycQoG3NQKtO5enrljexrfN6Q+fSC 92SZujPpaQ3oQ1fu9j5pvGIFhx9XO5PHwhgGJ/44wLpE4eiut0tSAljRwiFIqzZ2Ruox dn8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from; bh=v5G9ULfbzIgEe8IdW+aaLBrS7+28joajCIHKi8Gnm8Y=; b=St1Cp33k5u+cLRGSfLaOpsjxWzcrbhlBik03dqGgGisUzenIuFBZEwmBdwvq97Ldre w2cKgFBOxUaOsN4uakm1ZsJwog7jgHSvQB/tu8gVGGFSUiWj01GZ4ll8AZ4LSHhb47ej TZulsNcAyJ5J7rzNg0LTYmZPb3ZgDX5Uy0R1b5wNRxiSW8puGSD6EkNdDLplLtST86ok FFl0YalxOWlefBc6VQmAWT3PTQIYPqnZpKqMhyIiDblNBebVDPckv/2bhkTJUkMTmU+2 oV7t4qy7n1LeiRWXu8JPNZlVEXk9Y2iBbCbCmzXju9chL9JDkrqdbaFnZkdMsPhNqDci 9mbg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q11si7935908edn.225.2020.12.19.05.06.01; Sat, 19 Dec 2020 05:06:23 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728007AbgLSNEb (ORCPT + 99 others); Sat, 19 Dec 2020 08:04:31 -0500 Received: from mail.kernel.org ([198.145.29.99]:52376 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728536AbgLSNE1 (ORCPT ); Sat, 19 Dec 2020 08:04:27 -0500 From: Greg Kroah-Hartman Authentication-Results: mail.kernel.org; dkim=permerror (bad message/signature format) To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Alexander Sverdlin Subject: [PATCH 5.4 29/34] serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access Date: Sat, 19 Dec 2020 14:03:26 +0100 Message-Id: <20201219125342.828707060@linuxfoundation.org> X-Mailer: git-send-email 2.29.2 In-Reply-To: <20201219125341.384025953@linuxfoundation.org> References: <20201219125341.384025953@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Alexander Sverdlin commit d96f04d347e4011977abdbb4da5d8f303ebd26f8 upstream. It has been observed that once per 300-1300 port openings the first transmitted byte is being corrupted on AM3352 ("v" written to FIFO appeared as "e" on the wire). It only happened if single byte has been transmitted right after port open, which means, DMA is not used for this transfer and the corruption never happened afterwards. Therefore I've carefully re-read the MDR1 errata (link below), which says "when accessing the MDR1 registers that causes a dummy under-run condition that will freeze the UART in IrDA transmission. In UART mode, this may corrupt the transferred data". Strictly speaking, omap_8250_mdr1_errataset() performs a read access and if the value is the same as should be written, exits without errata-recommended FIFO reset. A brief check of the serial_omap_mdr1_errataset() from the competing omap-serial driver showed it has no read access of MDR1. After removing the read access from omap_8250_mdr1_errataset() the data corruption never happened any more. Link: https://www.ti.com/lit/er/sprz360i/sprz360i.pdf Fixes: 61929cf0169d ("tty: serial: Add 8250-core based omap driver") Cc: stable@vger.kernel.org Signed-off-by: Alexander Sverdlin Link: https://lore.kernel.org/r/20201210055257.1053028-1-alexander.sverdlin@gmail.com Signed-off-by: Greg Kroah-Hartman --- drivers/tty/serial/8250/8250_omap.c | 5 ----- 1 file changed, 5 deletions(-) --- a/drivers/tty/serial/8250/8250_omap.c +++ b/drivers/tty/serial/8250/8250_omap.c @@ -170,11 +170,6 @@ static void omap_8250_mdr1_errataset(str struct omap8250_priv *priv) { u8 timeout = 255; - u8 old_mdr1; - - old_mdr1 = serial_in(up, UART_OMAP_MDR1); - if (old_mdr1 == priv->mdr1) - return; serial_out(up, UART_OMAP_MDR1, priv->mdr1); udelay(2);