1. 01 5月, 2019 2 次提交
    • L
      irqchip/ti-sci-inta: Add support for Interrupt Aggregator driver · 9f1463b8
      Lokesh Vutla 提交于
      Texas Instruments' K3 generation SoCs has an IP Interrupt Aggregator
      which is an interrupt controller that does the following:
      - Converts events to interrupts that can be understood by
        an interrupt router.
      - Allows for multiplexing of events to interrupts.
      
      Configuration of the interrupt aggregator registers can only be done by
      a system co-processor and the driver needs to send a message to this
      co processor over TISCI protocol. Add the required infrastructure to
      allow the allocation and routing of these events.
      Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
      Signed-off-by: NMarc Zyngier <marc.zyngier@arm.com>
      9f1463b8
    • L
      irqchip/ti-sci-intr: Add support for Interrupt Router driver · cd844b07
      Lokesh Vutla 提交于
      Texas Instruments' K3 generation SoCs has an IP Interrupt Router
      that does allows for redirection of input interrupts to host
      interrupt controller. Interrupt Router inputs are either from a
      peripheral or from an Interrupt Aggregator which is another
      interrupt controller.
      
      Configuration of the interrupt router registers can only be done by
      a system co-processor and the driver needs to send a message to this
      co processor over TISCI protocol.
      
      Add support for Interrupt Router driver over TISCI protocol.
      Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
      Signed-off-by: NMarc Zyngier <marc.zyngier@arm.com>
      cd844b07
  2. 29 4月, 2019 1 次提交
  3. 19 2月, 2019 2 次提交
  4. 14 2月, 2019 1 次提交
  5. 18 12月, 2018 2 次提交
  6. 13 12月, 2018 1 次提交
  7. 26 10月, 2018 2 次提交
  8. 02 10月, 2018 1 次提交
  9. 13 8月, 2018 1 次提交
  10. 03 8月, 2018 2 次提交
    • P
      genirq/irqchip: Remove MULTI_IRQ_HANDLER as it's now obselete · 4f7799d9
      Palmer Dabbelt 提交于
      Now that every user of MULTI_IRQ_HANDLER has been convereted over to use
      GENERIC_IRQ_MULTI_HANDLER remove the references to MULTI_IRQ_HANDLER.
      Signed-off-by: NPalmer Dabbelt <palmer@sifive.com>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Cc: linux@armlinux.org.uk
      Cc: catalin.marinas@arm.com
      Cc: Will Deacon <will.deacon@arm.com>
      Cc: jonas@southpole.se
      Cc: stefan.kristiansson@saunalahti.fi
      Cc: shorne@gmail.com
      Cc: jason@lakedaemon.net
      Cc: marc.zyngier@arm.com
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: nicolas.pitre@linaro.org
      Cc: vladimir.murzin@arm.com
      Cc: keescook@chromium.org
      Cc: jinb.park7@gmail.com
      Cc: yamada.masahiro@socionext.com
      Cc: alexandre.belloni@bootlin.com
      Cc: pombredanne@nexb.com
      Cc: Greg KH <gregkh@linuxfoundation.org>
      Cc: kstewart@linuxfoundation.org
      Cc: jhogan@kernel.org
      Cc: mark.rutland@arm.com
      Cc: ard.biesheuvel@linaro.org
      Cc: james.morse@arm.com
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: openrisc@lists.librecores.org
      Link: https://lkml.kernel.org/r/20180622170126.6308-6-palmer@sifive.com
      4f7799d9
    • P
      irqchip: Port the ARM IRQ drivers to GENERIC_IRQ_MULTI_HANDLER · 08fb550c
      Palmer Dabbelt 提交于
      GENERIC_IRQ_MULTI_HANDLER is incompatible with MULTI_IRQ_HANDLER because
      they define the same symbols.  Multiple generic irqchip drivers select
      MULTI_IRQ_HANDLER, which is now defined on all architectures that
      provide set_handle_irq().
      
      To solve this select GENERIC_IRQ_MULTI_HANDLER for all drivers that used to
      select MULTI_IRQ_HANDLER, but only when MULTI_IRQ_HANDLER doesn't exist.
      
      After that every architecture can be converted over from MULTI_IRQ_HANDLER
      to GENERIC_IRQ_MULTI_HANDLER before removing the extra MULTI_IRQ_HANDLER
      scaffolding.
      Signed-off-by: NPalmer Dabbelt <palmer@sifive.com>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Cc: linux@armlinux.org.uk
      Cc: catalin.marinas@arm.com
      Cc: Will Deacon <will.deacon@arm.com>
      Cc: jonas@southpole.se
      Cc: stefan.kristiansson@saunalahti.fi
      Cc: shorne@gmail.com
      Cc: jason@lakedaemon.net
      Cc: marc.zyngier@arm.com
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: nicolas.pitre@linaro.org
      Cc: vladimir.murzin@arm.com
      Cc: keescook@chromium.org
      Cc: jinb.park7@gmail.com
      Cc: yamada.masahiro@socionext.com
      Cc: alexandre.belloni@bootlin.com
      Cc: pombredanne@nexb.com
      Cc: Greg KH <gregkh@linuxfoundation.org>
      Cc: kstewart@linuxfoundation.org
      Cc: jhogan@kernel.org
      Cc: mark.rutland@arm.com
      Cc: ard.biesheuvel@linaro.org
      Cc: james.morse@arm.com
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: openrisc@lists.librecores.org
      Cc: Shea Levy <shea@shealevy.com>
      Link: https://lkml.kernel.org/r/20180622170126.6308-2-palmer@sifive.com
      08fb550c
  11. 22 3月, 2018 1 次提交
  12. 14 3月, 2018 1 次提交
  13. 22 2月, 2018 1 次提交
  14. 04 1月, 2018 1 次提交
  15. 14 11月, 2017 1 次提交
    • M
      irqchip/gic-v3-its: Remove artificial dependency on PCI · 29f41139
      Marc Zyngier 提交于
      The GICv3 ITS doesn't really depend on PCI. Only the PCI/MSI
      part of it does, and there is no reason not to blow away most
      of the irqchip stack because PCI is not selected (though not
      selecting PCI seem to be asking for punishment, but hey...).
      
      So let's split the PCI-specific part from the ITS in the Kconfig
      file, and let's make that part depend on PCI. Architecture specific
      hacks (arch/arm{,64}/Kconfig) will be addressed in a separate patch.
      Reported-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NMarc Zyngier <marc.zyngier@arm.com>
      29f41139
  16. 07 11月, 2017 1 次提交
  17. 03 11月, 2017 1 次提交
  18. 20 10月, 2017 1 次提交
    • T
      irqchip/meson: Disable COMPILE_TEST · d9ee91c1
      Thomas Gleixner 提交于
      The driver fails to compile with CONFIG_COMPILE_TEST=y on x86:
      
      irq-meson-gpio.c: In function ‘meson_gpio_irq_parse_dt’:
      irq-meson-gpio.c:343:8: error: implicit declaration of function
      			       ‘of_property_read_variable_u32_array’
        ret = of_property_read_variable_u32_array(node,
      
      Adding COMPILE_TEST to a driver requires at least compile testing it for
      x86....
      Reported-by: NIngo Molnar <mingo@kernel.org>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Cc: Heiner Kallweit <hkallweit1@gmail.com>
      Cc: Jerome Brunet <jbrunet@baylibre.com>
      Cc: Marc Zyngier <marc.zyngier@arm.com>
      d9ee91c1
  19. 19 10月, 2017 1 次提交
  20. 17 10月, 2017 1 次提交
  21. 23 8月, 2017 1 次提交
  22. 18 8月, 2017 7 次提交
  23. 23 6月, 2017 2 次提交
  24. 15 6月, 2017 1 次提交
    • L
      ARM64/irqchip: Update ACPI_IORT symbol selection logic · c6bb8f89
      Lorenzo Pieralisi 提交于
      ACPI IORT is an ACPI addendum to describe the connection topology of
      devices with IOMMUs and interrupt controllers on ARM64 ACPI systems.
      
      Currently the ACPI IORT Kbuild symbol is selected whenever the Kbuild
      symbol ARM_GIC_V3_ITS is enabled, which in turn is selected by ARM64
      Kbuild defaults. This makes the logic behind ACPI_IORT selection a bit
      twisted and not easy to follow. On ARM64 systems enabling ACPI the
      kbuild symbol ACPI_IORT should always be selected in that it is a kernel
      layer provided to the ARM64 arch code to parse and enable ACPI firmware
      bindings.
      
      Make the ACPI_IORT selection explicit in ARM64 Kbuild and remove the
      selection from ARM_GIC_V3_ITS entry, making the ACPI_IORT selection
      logic clearer to follow.
      Acked-by: NHanjun Guo <hanjun.guo@linaro.org>
      Signed-off-by: NLorenzo Pieralisi <lorenzo.pieralisi@arm.com>
      Cc: Will Deacon <will.deacon@arm.com>
      Cc: Hanjun Guo <hanjun.guo@linaro.org>
      Cc: Catalin Marinas <catalin.marinas@arm.com>
      Cc: Marc Zyngier <marc.zyngier@arm.com>
      Signed-off-by: NWill Deacon <will.deacon@arm.com>
      c6bb8f89
  25. 13 4月, 2017 1 次提交
  26. 07 4月, 2017 1 次提交
    • L
      irqchip/gemini: Refactor Gemini driver to reflect Faraday origin · 6ee532e2
      Linus Walleij 提交于
      The Gemini irqchip turns out to be a standard IP component from
      Faraday Technology named FTINTC010 after some research and new
      information.
      
      - Rename the driver and all symbols to reflect the new information.
      - Add the new compatible string "faraday,ftintc010"
      - Create a Kconfig symbol CONFIG_FARADAY_FTINTC010 so that SoCs
        using this interrupt controller can easily select and reuse it
        instead of hardwiring it to ARCH_GEMINI
      
      I have created a separate patch to select the new Kconfig symbol
      from the Gemini machine, which will be merged through the ARM
      SoC tree.
      
      Cc: Greentime Hu <green.hu@gmail.com>
      Cc: Paulius Zaleckas <paulius.zaleckas@gmail.com>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NMarc Zyngier <marc.zyngier@arm.com>
      6ee532e2
  27. 14 3月, 2017 1 次提交
    • A
      irqchip/mvebu-odmi: Select GENERIC_MSI_IRQ_DOMAIN · fa23b9d1
      Arnd Bergmann 提交于
      This driver uses the MSI domain but has no strict dependency on PCI_MSI, so we
      may run into a build failure when CONFIG_GENERIC_MSI_IRQ_DOMAIN is disabled:
      
      drivers/irqchip/irq-mvebu-odmi.c:152:15: error: variable 'odmi_msi_ops' has initializer but incomplete type
       static struct msi_domain_ops odmi_msi_ops = {
                     ^~~~~~~~~~~~~~
      drivers/irqchip/irq-mvebu-odmi.c:155:15: error: variable 'odmi_msi_domain_info' has initializer but incomplete type
       static struct msi_domain_info odmi_msi_domain_info = {
                     ^~~~~~~~~~~~~~~
      drivers/irqchip/irq-mvebu-odmi.c:156:3: error: 'struct msi_domain_info' has no member named 'flags'
        .flags = (MSI_FLAG_USE_DEF_DOM_OPS | MSI_FLAG_USE_DEF_CHIP_OPS),
         ^~~~~
      drivers/irqchip/irq-mvebu-odmi.c:156:12: error: 'MSI_FLAG_USE_DEF_DOM_OPS' undeclared here (not in a function)
        .flags = (MSI_FLAG_USE_DEF_DOM_OPS | MSI_FLAG_USE_DEF_CHIP_OPS),
                  ^~~~~~~~~~~~~~~~~~~~~~~~
      drivers/irqchip/irq-mvebu-odmi.c:156:39: error: 'MSI_FLAG_USE_DEF_CHIP_OPS' undeclared here (not in a function); did you mean 'MSI_FLAG_USE_DEF_DOM_OPS'?
      
      Selecting the option from this driver seems to solve this nicely, though I could
      not find any other instance of this in irqchip drivers.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      Signed-off-by: NMarc Zyngier <marc.zyngier@arm.com>
      fa23b9d1
  28. 03 2月, 2017 1 次提交
    • A
      irqchip/qcom: Add IRQ combiner driver · f20cc9b0
      Agustin Vega-Frias 提交于
      Driver for interrupt combiners in the Top-level Control and Status
      Registers (TCSR) hardware block in Qualcomm Technologies chips.
      
      An interrupt combiner in this block combines a set of interrupts by
      OR'ing the individual interrupt signals into a summary interrupt
      signal routed to a parent interrupt controller, and provides read-
      only, 32-bit registers to query the status of individual interrupts.
      The status bit for IRQ n is bit (n % 32) within register (n / 32)
      of the given combiner. Thus, each combiner can be described as a set
      of register offsets and the number of IRQs managed.
      Signed-off-by: NAgustin Vega-Frias <agustinv@codeaurora.org>
      Signed-off-by: NMarc Zyngier <marc.zyngier@arm.com>
      f20cc9b0