Re: [Linaro-acpi] [PATCH v3 13/17] ARM64 / ACPI: Add GICv2 specific ACPI boot support

2014-09-05 Thread Tomasz Nowicki
On 05.09.2014 12:39, Marc Zyngier wrote: On 05/09/14 11:13, Arnd Bergmann wrote: On Friday 05 September 2014 10:47:30 Marc Zyngier wrote: I still prefer being explicit here for the same reason I mentioned earlier: I want it to be very clear that we don't support arbitrary irqchips other

Re: [Linaro-acpi] [PATCH v3 13/17] ARM64 / ACPI: Add GICv2 specific ACPI boot support

2014-09-05 Thread Marc Zyngier
On 05/09/14 11:13, Arnd Bergmann wrote: > On Friday 05 September 2014 10:47:30 Marc Zyngier wrote: >>> >>> I still prefer being explicit here for the same reason I mentioned earlier: >>> I want it to be very clear that we don't support arbitrary irqchips other >>> than the ones in the APCI

Re: [Linaro-acpi] [PATCH v3 13/17] ARM64 / ACPI: Add GICv2 specific ACPI boot support

2014-09-05 Thread Tomasz Nowicki
On 05.09.2014 12:13, Arnd Bergmann wrote: On Friday 05 September 2014 10:47:30 Marc Zyngier wrote: I still prefer being explicit here for the same reason I mentioned earlier: I want it to be very clear that we don't support arbitrary irqchips other than the ones in the APCI specification.

Re: [Linaro-acpi] [PATCH v3 13/17] ARM64 / ACPI: Add GICv2 specific ACPI boot support

2014-09-05 Thread Arnd Bergmann
On Friday 05 September 2014 10:47:30 Marc Zyngier wrote: > > > > I still prefer being explicit here for the same reason I mentioned earlier: > > I want it to be very clear that we don't support arbitrary irqchips other > > than the ones in the APCI specification. The infrastructure exists on DT >

Re: [Linaro-acpi] [PATCH v3 13/17] ARM64 / ACPI: Add GICv2 specific ACPI boot support

2014-09-05 Thread Arnd Bergmann
On Friday 05 September 2014 10:47:30 Marc Zyngier wrote: I still prefer being explicit here for the same reason I mentioned earlier: I want it to be very clear that we don't support arbitrary irqchips other than the ones in the APCI specification. The infrastructure exists on DT because

Re: [Linaro-acpi] [PATCH v3 13/17] ARM64 / ACPI: Add GICv2 specific ACPI boot support

2014-09-05 Thread Tomasz Nowicki
On 05.09.2014 12:13, Arnd Bergmann wrote: On Friday 05 September 2014 10:47:30 Marc Zyngier wrote: I still prefer being explicit here for the same reason I mentioned earlier: I want it to be very clear that we don't support arbitrary irqchips other than the ones in the APCI specification.

Re: [Linaro-acpi] [PATCH v3 13/17] ARM64 / ACPI: Add GICv2 specific ACPI boot support

2014-09-05 Thread Marc Zyngier
On 05/09/14 11:13, Arnd Bergmann wrote: On Friday 05 September 2014 10:47:30 Marc Zyngier wrote: I still prefer being explicit here for the same reason I mentioned earlier: I want it to be very clear that we don't support arbitrary irqchips other than the ones in the APCI specification. The

Re: [Linaro-acpi] [PATCH v3 13/17] ARM64 / ACPI: Add GICv2 specific ACPI boot support

2014-09-05 Thread Tomasz Nowicki
On 05.09.2014 12:39, Marc Zyngier wrote: On 05/09/14 11:13, Arnd Bergmann wrote: On Friday 05 September 2014 10:47:30 Marc Zyngier wrote: I still prefer being explicit here for the same reason I mentioned earlier: I want it to be very clear that we don't support arbitrary irqchips other

Re: [Linaro-acpi] [PATCH v3 13/17] ARM64 / ACPI: Add GICv2 specific ACPI boot support

2014-09-02 Thread Alexander Spyridakis
On 1 September 2014 19:35, Marc Zyngier wrote: > > On 01/09/14 15:57, Hanjun Guo wrote: > > From: Tomasz Nowicki > > > > ACPI kernel uses MADT table for proper GIC initialization. It needs to > > parse GIC related subtables, collect CPU interface and distributor > > addresses and call driver

Re: [Linaro-acpi] [PATCH v3 13/17] ARM64 / ACPI: Add GICv2 specific ACPI boot support

2014-09-02 Thread Alexander Spyridakis
On 1 September 2014 19:35, Marc Zyngier marc.zyng...@arm.com wrote: On 01/09/14 15:57, Hanjun Guo wrote: From: Tomasz Nowicki tomasz.nowi...@linaro.org ACPI kernel uses MADT table for proper GIC initialization. It needs to parse GIC related subtables, collect CPU interface and