Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp9447708pxu; Mon, 28 Dec 2020 16:55:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJyx9ruiuDNEtglqU6vMRdp6Qsog/tlvacYnDT8sU6oNhLRTg5MMa5HFk6N4wndkF1HkPIl0 X-Received: by 2002:a17:906:d0c2:: with SMTP id bq2mr43613447ejb.1.1609203332459; Mon, 28 Dec 2020 16:55:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1609203332; cv=none; d=google.com; s=arc-20160816; b=qRsjXYGCrW9qOd3mSemLooj9YuB1c50W34ubpjpv1cFPQBKBOTrZ2w18rWktmEzTWl aG+jOvR+TfaloyFGtdU7IrvPSLQc3Vaz1+XOZYYRMTFvkelPPJfx1DlLKumU6QnzQpQ6 X+8E+7CYyBMQUfrBoxOJjoxC/C4C5NhI8a1od4+H1tVNa2NwVtOaRIJs+nA9esZmElyT dnok4Vnd4xZUmVdHex5H50emRMhoqmmSfajGfd83BpowfC8uTRSqXwJOLh6zx5qHQz9s XUM0uHGQF5hbSokBWM3/eZh/ZFZ5WAIu2JuH5YRc6fIaWzLk4b6BRSKHiZ+ANjj8KsMS mlOw== 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:dkim-signature; bh=uHvWgiyhe5x0LDtMR0iI5B8Ml9rSb2yNhR3OpMRl/SU=; b=DZnMnhQyxfyjeizBHYBYa4vN8Ac/gutTY8kt/g2QuIY+Qw9KV3ZIcn7wsFYFJNWtpZ 1VOJgSFhHvpRkTaxD962CnIzi1quo81oiKWQ85K/gwhcdSKiXr66qPFRX6gsf5rQmqaf QlzF8sA+L7pRuriFuLpc3e2xxDG6emQpeg18thHq7oPPwVLlxSIXFDHv1ncMyVDcJeSD 7PMeVl3e2YR5N737lWBuWoOYnknidV2u5knm5KRn59x7ZX6/nsduIMoeFnh1FrUi+08Y LymFelB8h7ZrkppgiURaJOLOV60xqmtzJNMA8inxZzJAeoG+v5FAFo9W9lkG3BwRvdpA aCHA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=rWhSuYL+; 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=pass (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 z21si22203934edr.365.2020.12.28.16.55.10; Mon, 28 Dec 2020 16:55:32 -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; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=rWhSuYL+; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731546AbgL1QMe (ORCPT + 99 others); Mon, 28 Dec 2020 11:12:34 -0500 Received: from mail.kernel.org ([198.145.29.99]:49632 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388078AbgL1NV0 (ORCPT ); Mon, 28 Dec 2020 08:21:26 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 36066207CF; Mon, 28 Dec 2020 13:21:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1609161670; bh=MQH0UekFCSqVDxfI5w99oZSia+ZQgBruD/ikSCaCVlw=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=rWhSuYL+6kTgS5l9ytuEIE09UdrBfLdpLOrmIgxkqYO4KzdD6aT4g57dgUimbQk1V Y+OjdRnr4GkJP6mAc0o09GAGcdrQAGccTgY5jpHoPkCMPVXxt7dI1NoWDsgGZK4yrf jaPKO8+r/YiS3lqYU1GMG+X8Wh8VWJuvZGl/4CBY= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Alexander Sverdlin Subject: [PATCH 4.19 047/346] serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access Date: Mon, 28 Dec 2020 13:46:06 +0100 Message-Id: <20201228124922.065576597@linuxfoundation.org> X-Mailer: git-send-email 2.29.2 In-Reply-To: <20201228124919.745526410@linuxfoundation.org> References: <20201228124919.745526410@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 @@ -163,11 +163,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);