For MSI I doubt any. I think on some parts we might have two (or
more) groups of MSIs.
However I want to be able to handle timers and the slightly more
generic message interrupts.
You can probably add a reg and a ranges, the reg remains the same
as today as to not inflict any
On Freescale open-pic controllers we have a number of additional
features not spec'd per openpic. (additional timers, perf mon, PCIe
msi, message interrupts, ...). The problem is how to identify these
features in the device tree.
For example we have:
m...@41600 {
On Mon, Feb 16, 2009 at 10:58:42AM -0600, Kumar Gala wrote:
On Freescale open-pic controllers we have a number of additional
features not spec'd per openpic. (additional timers, perf mon, PCIe
msi, message interrupts, ...). The problem is how to identify these
features in the device
On Feb 16, 2009, at 12:12 PM, Scott Wood wrote:
On Mon, Feb 16, 2009 at 10:58:42AM -0600, Kumar Gala wrote:
On Freescale open-pic controllers we have a number of additional
features not spec'd per openpic. (additional timers, perf mon, PCIe
msi, message interrupts, ...). The problem is how
