Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp2874753pxu; Sat, 19 Dec 2020 05:01:47 -0800 (PST) X-Google-Smtp-Source: ABdhPJzEDkSyC05O8Ke469LlRpcBgx30EokGqvbIENY2+B5o4WBxG/by2tKKqS10se0p159P8qZU X-Received: by 2002:a17:906:d62:: with SMTP id s2mr8306480ejh.61.1608382906822; Sat, 19 Dec 2020 05:01:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1608382906; cv=none; d=google.com; s=arc-20160816; b=yNRV5zI1gDsyDjEtsU898+MZNNW62bu57Tt3SsN2v2zA4PKixWJm6mdfLALkB93ckl AL7kCMzijvWcYh3OZGvFHdB7mV/5yb20Wxv85XCgjGAzwk1SQF/hPfrFAsEiwxqWa8Mm bNFR9Zwa+sj6vf6V6HK+DczwUXWd5t0jFhDs7gDtY8oDdt/rTsb3kICTvf4vU2qgyWNn ASGvX8O+CK2FbllIt7ayVbUG/T9g/wao1z91ymSbEnTsNeOuD0sqwlNdHIN56iHMUPDS ATUCMzcZ3mCje8Yzi5QS1evo1yRI5QVnD4dhkIj+BsejVO7LYhby8xcY2c9KBn1fehi3 3X0g== 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=nkQdLPldDzfb8JbQN+ldOGzJGBCLwTbFTAhChR6qx/8=; b=ukbQG+lLDQKM4xrAdfY8Bd8cqyK1wZkHeyoUGKjV+Bs6fQD/H9g73+rzS/H+426iMQ wSV+fnAUHA7rowdX/d7zTV4sj+kL9FFawVEwG3GVToLH+R3zL9oDEwcAbMwA2ptQubwq BmwrYNv2QsOvvktMsYYnrvGjesO1zVVr2KKb/cttydBseqD6OTyZCDgM3hLmN+qHAZzc MfziloT6nvSurShWyXTRb4w+c9BMhH4XRcK5n3SdCS30OYmT2XEhY8zuxIkcnQi5If1N +eO2AT7YcqOnUjGiKDrg63kRm/a0R1t8henkMfbBtHpz4RIv6IhV1w6auai0jjBOHjN3 2DFg== 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 a2si6122047ejp.666.2020.12.19.05.01.24; Sat, 19 Dec 2020 05:01:46 -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 S1728455AbgLSNAJ (ORCPT + 99 others); Sat, 19 Dec 2020 08:00:09 -0500 Received: from mail.kernel.org ([198.145.29.99]:46634 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728270AbgLSM7i (ORCPT ); Sat, 19 Dec 2020 07:59:38 -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.9 45/49] serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access Date: Sat, 19 Dec 2020 13:58:49 +0100 Message-Id: <20201219125346.872315993@linuxfoundation.org> X-Mailer: git-send-email 2.29.2 In-Reply-To: <20201219125344.671832095@linuxfoundation.org> References: <20201219125344.671832095@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 @@ -184,11 +184,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);