Message ID | 20221107110708.58223-1-ilpo.jarvinen@linux.intel.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:6687:0:0:0:0:0 with SMTP id l7csp1980709wru; Mon, 7 Nov 2022 03:08:01 -0800 (PST) X-Google-Smtp-Source: AMsMyM55a+ErRv0DYU6htfr/Gk81L/4fa2zan/7t30KZGJsKX9SHck7G84RlfYGRPuWhruToUVQs X-Received: by 2002:aa7:da84:0:b0:463:7873:119a with SMTP id q4-20020aa7da84000000b004637873119amr38246131eds.329.1667819281639; Mon, 07 Nov 2022 03:08:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1667819281; cv=none; d=google.com; s=arc-20160816; b=rcPFpVIuoILdQVdr7XooRVSf6Dcr9HB91TlpZsfY4TO030DkWS50V9txOFCNHDP7MP wS/1E1XZufo/4/2iIDWV5Djee21GTK3O1ZrJVKuhhIeHXPi0lFRv0Y1ss2DHXWuuOuwa bodKm96RW/RGkzk7s/Ba/L/0jtp3d4qMigJ0lr+astA4izc3jCLljpZZz6kyXkN8Oz36 yZp7p7xz10JuK0rR+sM0pFHKQlMg4va+jVQTTeU/D2tlfAWWVtdyP4Xtvg+jXvbirFju v9S4y6gZg1Q6UzWjhiegdcLvp1ftwctUOEx74KI8fQRF1WyNlYRm3NdMYj0B1J2HPs0D dqmw== 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 :message-id:date:subject:cc:to:from:dkim-signature; bh=9jHtNec2Fzrf3Y4STzg95JAC6+36/k8zEBEaTeVQuDQ=; b=gIRAIr89DXLBHKI7KzH6xq+c0uC6m1O7usBQgxzCR7ygnFtZj7LtY4CGC5owKp4fhv jMLgHsUt3UcA84e5pnysCod5aO8XRPVYphivXuPGDzeC6uR8yjTIhSRfipJ8v6SA+3c3 fgePnnSehwXYSaov2g8t8Wcv6g/WhQQ7LV6qqMDiKbf3EEcztDXlChCuxAfVtzpf+KB3 eYfGx8Ivq4FyhuKnrFr0b/oUICUacyKtxutyc6EYtcE2qp7Uld1Pq0BkCQljo1q55kId BhyOvp+U2yjJm6aYG6T0n6WPTw/SjPEceBkQ0z7ikmvqmteYfk+x5BNHjCJxHYhNxJkY Nc0Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=AETYgtV4; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ne25-20020a1709077b9900b007adc4a0aeb5si9096194ejc.873.2022.11.07.03.07.37; Mon, 07 Nov 2022 03:08:01 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=AETYgtV4; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231431AbiKGLHd (ORCPT <rfc822;hjfbswb@gmail.com> + 99 others); Mon, 7 Nov 2022 06:07:33 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60210 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231419AbiKGLHT (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 7 Nov 2022 06:07:19 -0500 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7F53218383; Mon, 7 Nov 2022 03:07:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1667819238; x=1699355238; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=Sm+yS9utvJpJAQMRMEurAzuv8xjSarjiRadqA2mVG6E=; b=AETYgtV4N1Y1K+7ai16LtBN46J8bJe4dtbsyr7iwBjOPBPMg5SYmxuhS 6QSSA+PYoi+3npDZBjCe2WzLQFkLNCzA2WXrWr94hRoBHFj2pLi10oDYm ges6cJqy3bJdS8g0eKPAIgG48HoS/4LhA2t3+cog4CFA7FMmy8Fvvxljq fN3vrrqNXoWSlEoqJLExKWGmm6Ergj2aut5XcdZlFm/ItX/F3Q7UyqlQ2 XrX0l65hRg6L9E+sJPmP+t9OolyrA2FDbELODFQvtP1pGUoIYWFjG0plo O5tmXu5mlxwbyixuSciN4dyzmWUO8K9y+tIu+eO5+mvq2DKcYpZsK8c+t A==; X-IronPort-AV: E=McAfee;i="6500,9779,10523"; a="290773000" X-IronPort-AV: E=Sophos;i="5.96,143,1665471600"; d="scan'208";a="290773000" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Nov 2022 03:07:18 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10523"; a="586932308" X-IronPort-AV: E=Sophos;i="5.96,143,1665471600"; d="scan'208";a="586932308" Received: from gschoede-mobl1.ger.corp.intel.com (HELO ijarvine-MOBL2.ger.corp.intel.com) ([10.252.46.211]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Nov 2022 03:07:15 -0800 From: =?utf-8?q?Ilpo_J=C3=A4rvinen?= <ilpo.jarvinen@linux.intel.com> To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Jiri Slaby <jirislaby@kernel.org>, linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org Cc: =?utf-8?q?Ilpo_J=C3=A4rvinen?= <ilpo.jarvinen@linux.intel.com> Subject: [PATCH 0/4] 8250: DMA Fixes Date: Mon, 7 Nov 2022 13:07:04 +0200 Message-Id: <20221107110708.58223-1-ilpo.jarvinen@linux.intel.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1748835270834676953?= X-GMAIL-MSGID: =?utf-8?q?1748835270834676953?= |
Series | 8250: DMA Fixes | |
Message
Ilpo Järvinen
Nov. 7, 2022, 11:07 a.m. UTC
Here are a number of 8250 DMA related fixes. The last one seems the most serious problem able to corrupt the payload ordering. Ilpo Järvinen (4): serial: 8250: Fall back to non-DMA Rx if IIR_RDI occurs serial: 8250_lpss: Configure DMA also w/o DMA filter serial: 8250_lpss: Use 16B DMA burst with Elkhart Lake serial: 8250: Flush DMA Rx on RLSI drivers/tty/serial/8250/8250_lpss.c | 18 +++++++++++++----- drivers/tty/serial/8250/8250_port.c | 7 +++++-- 2 files changed, 18 insertions(+), 7 deletions(-)
Comments
On Mon, Nov 07, 2022 at 01:07:04PM +0200, Ilpo Järvinen wrote: > Here are a number of 8250 DMA related fixes. The last one seems the > most serious problem able to corrupt the payload ordering. > > Ilpo Järvinen (4): > serial: 8250: Fall back to non-DMA Rx if IIR_RDI occurs 8250_port? > serial: 8250_lpss: Configure DMA also w/o DMA filter > serial: 8250_lpss: Use 16B DMA burst with Elkhart Lake > serial: 8250: Flush DMA Rx on RLSI 8250_port? > > drivers/tty/serial/8250/8250_lpss.c | 18 +++++++++++++----- > drivers/tty/serial/8250/8250_port.c | 7 +++++-- > 2 files changed, 18 insertions(+), 7 deletions(-)
On Mon, 7 Nov 2022, Andy Shevchenko wrote: > On Mon, Nov 07, 2022 at 01:07:04PM +0200, Ilpo Järvinen wrote: > > Here are a number of 8250 DMA related fixes. The last one seems the > > most serious problem able to corrupt the payload ordering. > > > > Ilpo Järvinen (4): > > serial: 8250: Fall back to non-DMA Rx if IIR_RDI occurs > > 8250_port? > > > serial: 8250_lpss: Configure DMA also w/o DMA filter > > serial: 8250_lpss: Use 16B DMA burst with Elkhart Lake > > serial: 8250: Flush DMA Rx on RLSI > > 8250_port? Why? To me this 8250_core/port split is still integral part of the same 8250 even if they're in the end technically loaded into different modules or the code is in a different file. There's even some trickery to access internals of the other part to workaround the circular module dependency logic that would otherwise prevent the split (like we learned not so long time ago with that setup_irq change). I can start to use 8250_port if you insist but it seems pointless 5 extra characters out from a resource that is scarse to begin with, IMHO (the summary line is not that long).