On Monday 13 January 2014, Ravi Patel wrote: > > For inbound messages, the QMTM serves a similar purpose as an MSI > > controller, ensuring that inbound DMA data has arrived in RAM > > before an interrupt is delivered to the CPU and thereby avoiding > > the need for an expensive MMIO read to serialize the DMA. > > For inbound messages, slave device generates message on a completion > of a inbound DMA operation or any relevant operation targeted to the > CPU. The QMTM's role is to just trigger an interrupt to CPU when there > is a new message arrived from a slave device. QMTM doesn't know what > the message was for. It is upto the upper layer drivers to decide how > to process this message. That doesn't seem to contradict what I wrote above. The DMA ordering would be an implicit side-effect of the message generated by the slave device if the QMTM is on the same bus as the external memory controller and the message has the "strict ordering" bit set on the bus transaction. Arnd -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
