Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1605815
| From | Russell King - ARM Linux <linux@armlinux.org.uk> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 05/20] ARM: implement pci_remap_cfgspace() interface |
| Date | 2017-03-21 18:00 +0100 |
| Message-ID | <tnviy-5Yp-17@gated-at.bofh.it> (permalink) |
| References | <tfvfH-7o7-3@gated-at.bofh.it> <tfvpo-7rK-21@gated-at.bofh.it> <tn8OZ-7wZ-1@gated-at.bofh.it> <tntTs-5b0-39@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Mar 21, 2017 at 03:26:36PM +0000, Lorenzo Pieralisi wrote: > I assumed that in plain terms, the difference between MT_DEVICE and > MT_UNCACHED is write posting (aka bufferable) behaviour (across CPU > architecture versions) and that does not affect write ordering rules. Having looked it up in the ARM ARM, I think we're fine. Device and strongly ordered accesses are both ordered as one group, so can be thought of as the same. The only difference is that Device can complete from the CPU's perspective before it hits the peripheral, whereas strongly ordered only completes once it's hit the peripheral. So this looks like exactly the right thing to do here. -- RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH 05/20] ARM: implement pci_remap_cfgspace() interface Russell King - ARM Linux <linux@armlinux.org.uk> - 2017-03-20 18:00 +0100
Re: [PATCH 05/20] ARM: implement pci_remap_cfgspace() interface Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> - 2017-03-21 16:30 +0100
Re: [PATCH 05/20] ARM: implement pci_remap_cfgspace() interface Russell King - ARM Linux <linux@armlinux.org.uk> - 2017-03-21 18:00 +0100
csiph-web