Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp18056510ybl; Thu, 2 Jan 2020 17:35:41 -0800 (PST) X-Google-Smtp-Source: APXvYqyMlO4rR/2tKa9Bia3DVEfBX6pPNFc0flJ9+hAJVQ0f5pCtAx3a0FfOxHDva0BDscbfdnH5 X-Received: by 2002:a9d:5888:: with SMTP id x8mr91595105otg.361.1578015340960; Thu, 02 Jan 2020 17:35:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578015340; cv=none; d=google.com; s=arc-20160816; b=Ua4FYHhYO6vnFS34llDwWxZ+fcSiZkAxgOcRMemka8N5HW03lJiKgFXvRVMRVtmMlS +y+RHKmkGXGFvlutdnj3x0HU0ePuPHo1iVFMWSaqCF+YrYthu+wYipbS6wLGa7WlggQZ 8p5IRSdJuhVEDzbE/Q4itEDivFfsjKpzqIOhLFpOLj9YGBKLyxYjkHaSW9L+RngeL8DK V6v5pZzpKsHlxUWTTtdX6vsc7jZis8FxVORzaX/XjCrwNYzYtCSShARMAH8zorImSBKX RZm2Hi272zbEu4GtSJg8TYG0AYd+76gb4MqLpaMrOdxE2NahQ5DP1efefpB3GxbRDU5C DJmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=W6LmiI8e/rAwjkN+F5cS5XQMnHPVRToO8K2WizgQSpE=; b=TLeE5cgIjJh0I9lsK5Znid9yyRZ9JsX7UmOiU9KkHGpPPouj5ikX5QpKjgNXe6fuDi 3cjhMbg4p/8FS+vHJ1r1O+SzQ01PQlHPAnGL1pbOq2bxT9CwCYE1/Zuoy1T6QaNwx7uv xMrAQATGKykYILjrHyfrzAWX8kUC3pjx6uXSrLKA+HUxMYHE7k+kqJZMZ7nqOUo24/j9 xxpyaAQGXsT3GxVpgGHyprZGMTKhM/f2wH60fS2i+GSYtrkHp+9Ayk43sb0uJkAPEO2u zpBkHVDGxUTwdod6P64lgsp8X3l4RUIzoAFEDLWBsTNRz2VuMXH3OFrxLYfmR57un+B8 m8Uw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i10si30937265otk.195.2020.01.02.17.35.27; Thu, 02 Jan 2020 17:35:40 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726219AbgACBeo (ORCPT + 99 others); Thu, 2 Jan 2020 20:34:44 -0500 Received: from szxga04-in.huawei.com ([45.249.212.190]:8659 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725872AbgACBeo (ORCPT ); Thu, 2 Jan 2020 20:34:44 -0500 Received: from DGGEMS408-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 2C7D0E5B6DDB8F977E82; Fri, 3 Jan 2020 09:34:42 +0800 (CST) Received: from [127.0.0.1] (10.57.64.164) by DGGEMS408-HUB.china.huawei.com (10.3.19.208) with Microsoft SMTP Server id 14.3.439.0; Fri, 3 Jan 2020 09:34:34 +0800 Subject: Re: [PATCH] spi: dw: use "smp_mb()" to avoid sending spi data error To: Mark Brown CC: , , , fengsheng , kXinwei Kong References: <1577352088-35856-1-git-send-email-kong.kongxinwei@hisilicon.com> <20191227002239.GH27497@sirena.org.uk> <20200103010409.GG3897@sirena.org.uk> From: kongxinwei Message-ID: Date: Fri, 3 Jan 2020 09:34:33 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20200103010409.GG3897@sirena.org.uk> Content-Type: text/plain; charset="windows-1252" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.57.64.164] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020/1/3 9:04, Mark Brown wrote: > On Sat, Dec 28, 2019 at 04:31:53PM +0800, kongxinwei wrote: > >>> I'd be much more comfortable here if I understood what this was >>> supposed to be syncing - what exactly gets flushed here and why >>> is a memory barrier enough to ensure it's synced? A comment in >>> the code would be especially good so anyone modifying the code >>> understands this in future. > >> Because of out-of-order execution about some CPU architecture, >> In this debug stage we find Completing spi interrupt enable -> >> prodrucing TXEI interrupt -> running "interrupt_transfer" function >> will prior to set "dw->rx and dws->rx_end" data, so it will result >> in SPI sending error > > Could you update the commit message to say that, and ideally also > add a comment saying something like "Ensure dw->rx and dw->rx_end > are visible" please? > OK, i WILL update it.