Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1293987

Re: [PATCH v4 1/5] PCI: designware: add memory barrier after enabling region

From Stanimir Varbanov <stanimir.varbanov@linaro.org>
Newsgroups linux.kernel
Subject Re: [PATCH v4 1/5] PCI: designware: add memory barrier after enabling region
Date 2015-12-17 16:50 +0100
Message-ID <qGIYy-1kc-9@gated-at.bofh.it> (permalink)
References (1 earlier) <qBCh4-5K6-9@gated-at.bofh.it> <qDmrw-ks-3@gated-at.bofh.it> <qDERr-3xo-1@gated-at.bofh.it> <qDKau-75S-9@gated-at.bofh.it> <qEnbQ-7u0-15@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 12/11/2015 06:05 AM, Pratyush Anand wrote:
> On Wed, Dec 9, 2015 at 3:53 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> 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/

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

Re: [PATCH v4 1/5] PCI: designware: add memory barrier after enabling  region Stanimir Varbanov <stanimir.varbanov@linaro.org> - 2015-12-17 16:50 +0100
  Re: [PATCH v4 1/5] PCI: designware: add memory barrier after enabling region Pratyush Anand <pratyush.anand@gmail.com> - 2015-12-17 17:00 +0100

csiph-web