On Wed, 20 Sep 2006, Bill Waddington wrote:
> On Wed, 20 Sep 2006 19:10:55 UTC, in fa.linux.kernel you wrote:
>> On Wed, 20 Sep 2006, Alan Stern wrote:
>>> I've heard that to insure proper synchronization it's necessary to flush
>>> MMIO writes (writel, writew, writeb) to PCI devices by reading from the
>>> same area. Is this equally true for I/O-space writes (inl, inw, inb)?
>>> What about configuration space writes (pci_write_config_dword etc.)?
>>> Alan Stern
>> Writes to I/O space are not queued through a FIFO so there is
>> no need to flush the FIFO. Configuration space uses special
>> configuration cycles which are handshakes with the devices. They
>> cannot be queued, therefore don't need to be flushed either.
>> Flushing PCI space writes shouldn't be done until you want
>> whatever you've been planning to happen __now__. Otherwise
>> the advantages of queued writes go away. In other words, one
>> should NOT attach a read to every PCI space write! Typically
>> use of the flushing read might be in the case of setting up
>> hardware for a DMA transfer. You write all the data, source
>> address, destination address, byte-count, DMA type, etc., then
>> after the last instruction, the one should should start the DMA,
>> you issue a read.
> Are there ever any issues with out-of-order writes from the posting
> buffer on supported architectures? I can (barely) imagine a device
> that has the register with the start bit lower in the register address
> space than the count/address registers. Out-of-order writes from
> the cache/non-fifo/posting buffer (maybe to assemble a burst) could
> make the occasional mess.
> Just wondering,
> William D Waddington
> [email protected]
> "Even bugs...are unexpected signposts on
> the long road of creativity..." - Ken Burtch
People who make PCI interface chips like PLX would never make
devices that couldn't work on the PCI bus. However, it is possible
for somebody to make byte-wide or word-wide setup registers on
their local bus, accessed through an interface chip such as the PLX,
that might suffer because of write-combining. However, such defective
designs shouldn't make it to production.
Also, the PLX and other such interface chips don't rely upon
initialization order (like the PC 8237A DMA chips) when setting
up for a DMA transfer. They have a specific instruction to start
Penguin : Linux version 188.8.131.52 on an i686 machine (5592.66 BogoMips).
New book: http://www.AbominableFirebug.com/
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Video 4 Linux]
[Linux for the blind]