Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967141AbbLQPpr (ORCPT ); Thu, 17 Dec 2015 10:45:47 -0500 Received: from mail-wm0-f47.google.com ([74.125.82.47]:38671 "EHLO mail-wm0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934533AbbLQPpp (ORCPT ); Thu, 17 Dec 2015 10:45:45 -0500 Subject: Re: [PATCH v4 1/5] PCI: designware: add memory barrier after enabling region To: Pratyush Anand , Russell King - ARM Linux References: <1449149725-27607-1-git-send-email-stanimir.varbanov@linaro.org> <1449149725-27607-2-git-send-email-stanimir.varbanov@linaro.org> <56669C50.9060700@linaro.org> <20151209102359.GF8644@n2100.arm.linux.org.uk> Cc: Stanimir Varbanov , Arnd Bergmann , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, "linux-arm-kernel@lists.infradead.org" , "devicetree@vger.kernel.org" , "linux-pci@vger.kernel.org" , Bjorn Helgaas , Jingoo Han , Srinivas Kandagatla , Rob Herring , Rob Herring , Mark Rutland , Pawel Moll , Ian Campbell , Bjorn Andersson From: Stanimir Varbanov Message-ID: <5672D8A1.2080407@linaro.org> Date: Thu, 17 Dec 2015 17:45:37 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1708 Lines: 50 On 12/11/2015 06:05 AM, Pratyush Anand wrote: > On Wed, Dec 9, 2015 at 3:53 PM, Russell King - ARM Linux > wrote: > > [...] > >>>>> dw_pcie_writel_rc(pp, PCIE_ATU_ENABLE, PCIE_ATU_CR2); >>>>> + /* >>>>> + * ensure that the ATU enable has been happaned before accessing >>>>> + * pci configuration/io spaces through dw_pcie_cfg_[read|write]. >>>>> + */ >>>>> + wmb(); >>>>> } >>>>> >>> >>> >>> My understnading is that since writel() of dw_pcie_writel_rc() in >>> above code and readl(), writel() of dw_pcie_cfg_[read|write]() (which >>> will follow) goes through same device (ie PCIe host here). So, it is >>> guaranteed that 1st writel() will be executed before later >>> readl()/writel(). If that is true then we do not need any explicit >>> barrier here. >>> >>> Arnd, Russel: whats your opinion here. >> ^l > > Sorry :( > >> >> writel() has a barrier _before_ the access but not after. >> >> The fact is that there's nothing which guarantees that the write will hit >> the hardware in a timely manner (forget any rules about PCI config space, >> the PCI ordering rules apply to the PCI bus, not to the ARM buses.) >> >> If you need this write to have hit the hardware before continuing, you >> need to read back from the same register. > > OK, so better to replace wmb() with read back of control register. Would the patch be acceptable if I replace wmb with read? -- regards, Stan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/