[PATCH v2 2/2] powerpc/powernv: Don't alloc IRQ map if necessary

2015-01-22 Thread Gavin Shan
On PowerNV platform, the OPAL interrupts are exported by firmware through device-node property (/ibm,opal::opal-interrupts). Under some extreme circumstances (e.g. simulator), we don't have this property found from the device tree. For that case, we shouldn't allocate the interrupt map. Otherwise,

Re: powerpc/powernv: Don't alloc IRQ map if necessary

2015-01-21 Thread Gavin Shan
On Thu, Jan 22, 2015 at 04:54:59PM +1100, Michael Ellerman wrote: >On Thu, 2015-08-01 at 05:42:32 UTC, Gavin Shan wrote: >> On PowerNV platform, the OPAL interrupts are exported by firmware >> through device-node property (/ibm,opal::opal-interrupts). Under >> some extreme circumstances (e.g. simul

Re: powerpc/powernv: Don't alloc IRQ map if necessary

2015-01-21 Thread Michael Ellerman
On Thu, 2015-08-01 at 05:42:32 UTC, Gavin Shan wrote: > On PowerNV platform, the OPAL interrupts are exported by firmware > through device-node property (/ibm,opal::opal-interrupts). Under > some extreme circumstances (e.g. simulator), we don't have this > property found from the device tree. For t

[PATCH] powerpc/powernv: Don't alloc IRQ map if necessary

2015-01-07 Thread Gavin Shan
On PowerNV platform, the OPAL interrupts are exported by firmware through device-node property (/ibm,opal::opal-interrupts). Under some extreme circumstances (e.g. simulator), we don't have this property found from the device tree. For that case, we shouldn't allocate the interrupt map. Otherwise,