On Wed, Mar 11, 2015 at 08:39:42PM +0800, Hanjun Guo wrote: > From: Tomasz Nowicki <tomasz.nowicki@xxxxxxxxxx> > > 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 initialization function (which is hardware > abstraction agnostic). In a similar way, FDT initialize GICv1/2. > > NOTE: This commit allow to initialize GICv1/2 basic functionality. > While now simple GICv2 init call is used, any further GIC features > require generic infrastructure for proper ACPI irqchip initialization. > That mechanism and stacked irqdomains to support GICv2 MSI/virtualization > extension, GICv3/4 and its ITS are considered as next steps. > > CC: Jason Cooper <jason@xxxxxxxxxxxxxx> > CC: Marc Zyngier <marc.zyngier@xxxxxxx> > CC: Thomas Gleixner <tglx@xxxxxxxxxxxxx> > Tested-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@xxxxxxx> > Tested-by: Yijing Wang <wangyijing@xxxxxxxxxx> > Tested-by: Mark Langsdorf <mlangsdo@xxxxxxxxxx> > Tested-by: Jon Masters <jcm@xxxxxxxxxx> > Tested-by: Timur Tabi <timur@xxxxxxxxxxxxxx> > Tested-by: Robert Richter <rrichter@xxxxxxxxxx> > Acked-by: Robert Richter <rrichter@xxxxxxxxxx> > Reviewed-by: Grant Likely <grant.likely@xxxxxxxxxx> > Signed-off-by: Tomasz Nowicki <tomasz.nowicki@xxxxxxxxxx> > Signed-off-by: Hanjun Guo <hanjun.guo@xxxxxxxxxx> > --- > arch/arm64/include/asm/acpi.h | 2 + > arch/arm64/include/asm/irq.h | 13 +++++ > arch/arm64/kernel/acpi.c | 25 +++++++++ > drivers/irqchip/irq-gic.c | 102 +++++++++++++++++++++++++++++++++++ > drivers/irqchip/irqchip.c | 3 ++ > include/linux/acpi_irq.h | 10 ++++ > include/linux/irqchip/arm-gic-acpi.h | 31 +++++++++++ > 7 files changed, 186 insertions(+) > create mode 100644 include/linux/acpi_irq.h > create mode 100644 include/linux/irqchip/arm-gic-acpi.h Acked-by: Jason Cooper <jason@xxxxxxxxxxxxxx> thx, Jason. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html