On Wed, Mar 11, 2015 at 08:39:42PM +0800, Hanjun Guo wrote: > From: Tomasz Nowicki <[email protected]> > > 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 <[email protected]> > CC: Marc Zyngier <[email protected]> > CC: Thomas Gleixner <[email protected]> > Tested-by: Suravee Suthikulpanit <[email protected]> > Tested-by: Yijing Wang <[email protected]> > Tested-by: Mark Langsdorf <[email protected]> > Tested-by: Jon Masters <[email protected]> > Tested-by: Timur Tabi <[email protected]> > Tested-by: Robert Richter <[email protected]> > Acked-by: Robert Richter <[email protected]> > Reviewed-by: Grant Likely <[email protected]> > Signed-off-by: Tomasz Nowicki <[email protected]> > Signed-off-by: Hanjun Guo <[email protected]> > --- > 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 <[email protected]> thx, Jason. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
