From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id AB9AEC433FE for ; Tue, 8 Nov 2022 12:47:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234189AbiKHMrX (ORCPT ); Tue, 8 Nov 2022 07:47:23 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33644 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234079AbiKHMrT (ORCPT ); Tue, 8 Nov 2022 07:47:19 -0500 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 56DF951C29; Tue, 8 Nov 2022 04:47: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=1667911638; x=1699447638; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=zvBFCIqzdoTj9UnYmptO+ryXyIdI3ESvdJd9r6IDuZA=; b=SkmUVBJYf6sES4vKCpC6lpcTFsQ3lpgOSOT0HSeWEmOjgMs3YI0cr5Kd F6ztZxuXTdnkBnXA0Z43JHFFsK2kxU5ZNJzPmzgQpnddvzWuhYevO7SXs TO1VKjEmhBIRTpvYa0D7KTnZ1YHVdleGWtwXe/OpXaBnmpxQqS2WLbJq/ cA9oWBVBqnCCf4ZmvOvzJUZMPyl3kaFjA3T0eIDOMmYWECXflWaaQECgR yfDzkFMmqSrS7EPSXuHm5TJNQ/gbrb1DlWhrkQ1TTb/trC9EqEpCxeUAE FSHFe4c6LQA2/4kwRO8KSK3yHAa7Pl8cGnyBB9p8cRk1doI19aMDYsThV Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10524"; a="374955747" X-IronPort-AV: E=Sophos;i="5.96,147,1665471600"; d="scan'208";a="374955747" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Nov 2022 04:47:17 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10524"; a="699910525" X-IronPort-AV: E=Sophos;i="5.96,147,1665471600"; d="scan'208";a="699910525" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga008.fm.intel.com with ESMTP; 08 Nov 2022 04:47:15 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1osO0Y-0098GB-0o; Tue, 08 Nov 2022 14:47:14 +0200 Date: Tue, 8 Nov 2022 14:47:13 +0200 From: Andy Shevchenko To: Ilpo =?iso-8859-1?Q?J=E4rvinen?= Cc: linux-serial@vger.kernel.org, Greg Kroah-Hartman , Jiri Slaby , linux-kernel@vger.kernel.org, Gilles BULOZ Subject: Re: [PATCH v2 0/4] 8250: DMA Fixes Message-ID: References: <20221108121952.5497-1-ilpo.jarvinen@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20221108121952.5497-1-ilpo.jarvinen@linux.intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-serial@vger.kernel.org On Tue, Nov 08, 2022 at 02:19:48PM +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. Thank you for the update! LGTM, Reviewed-by: Andy Shevchenko > v2: > - Tweak configure logic to match Andy's suggestion > - Cleaned up the tags from the oneliner patch > > 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 -- With Best Regards, Andy Shevchenko