+ - device_type : Should be "rapidio"
There is no OF binding, so no.
So, we need to define it.
If you want to. Until that has been done, don't use
a "device_type". Linux won't use it, anyway.
Do you have another ideas about that? Only remove it?
Using IP Block Revision is a
I don't think so. For one thing, it describes a version of
a cell design, not a version of an actual device. For another
thing, if I hear "8641" I know what you're talking about (sort
of, anyway), but I draw a blank stare if you say "v1.0". I'm
sure I'm not the only one. Concrete names are good.
From the different view ways, there are different results. Getting theversion from RapidIO IP revision register is clear to me. :)
But the rapidio node doesn't know or care what the interrupts
are connected to, and neither should it. That's what the
interrupt mapping recommended practice is for.
There are no rapidio device in it. Doorbell, msg are all parts of
For example, 8641 rapidio controller have 2 msg unit: msg0 and msg1.
They are not rapidio devices. Each msg unit has the tx_irq and rx_irq.
You want a #size-cells as well.
The size is not used in this sector, so no defined.
The size _is_ used; in the "ranges" property in this node,
for example. It is also needed to describe the "reg" for
any child node of this node.
A non-existant "#size-cells" means 1, and "#address-cells"
means 2, so in principle you could do without these
properties; but Linux doesn't parse the tree correctly in
that case (which reminds me, I have some more patches to
Ok, I'll add it in the next version for more religious.