Add support for IRQ combiners in the Top-level Control and Status Registers (TCSR) hardware block in Qualcomm Technologies chips. The first patch prevents the ACPI core from attempting to map IRQ resources with a valid ResourceSource as GSIs. The first patch adds support for ResourceSource/IRQ domain mapping and fixes IRQ probe deferral by allowing platform_device IRQ resources to be re-initialized from the corresponding ACPI IRQ resource. Both changes described above are conditional on the ACPI_GENERIC_GSI config. The third patch takes advantage of the new capabilities to implement the driver for the IRQ combiners. Tested on top of v4.9. Changes V8 -> V9: * Do not attempt the mapping for non-GSI IRQs during bus scan. * Make some public APIs private to drivers/acpi/irq.c since they are no longer used on other modules. Changes V7 -> V8: * Reorder patches to allow all new code to be under drivers/acpi/irq.c. * Change acpi_irq_get implementation to be more similar to of_irq_get to improve maintainability. Agustin Vega-Frias (3): ACPI: Generic GSI: Do not attempt to map non-GSI IRQs during bus scan ACPI: Add support for ResourceSource/IRQ domain mapping irqchip: qcom: Add IRQ combiner driver drivers/acpi/Makefile | 2 +- drivers/acpi/gsi.c | 98 ----------- drivers/acpi/irq.c | 280 +++++++++++++++++++++++++++++++ drivers/acpi/resource.c | 17 +- drivers/base/platform.c | 9 +- drivers/irqchip/Kconfig | 9 + drivers/irqchip/Makefile | 1 + drivers/irqchip/qcom-irq-combiner.c | 322 ++++++++++++++++++++++++++++++++++++ include/linux/acpi.h | 10 ++ 9 files changed, 647 insertions(+), 101 deletions(-) delete mode 100644 drivers/acpi/gsi.c create mode 100644 drivers/acpi/irq.c create mode 100644 drivers/irqchip/qcom-irq-combiner.c -- Qualcomm Datacenter Technologies, Inc. on behalf of the Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project. -- 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