@@ -188,7 +188,6 @@ static const struct msi_domain_template mvebu_icu_nsr_msi_template = {
.irq_mask = irq_chip_mask_parent,
.irq_unmask = irq_chip_unmask_parent,
.irq_eoi = irq_chip_eoi_parent,
- .irq_set_type = irq_chip_set_type_parent,
.irq_write_msi_msg = mvebu_icu_write_msi_msg,
.flags = IRQCHIP_SUPPORTS_LEVEL_MSI,
},
@@ -212,7 +211,6 @@ static const struct msi_domain_template mvebu_icu_sei_msi_template = {
.irq_mask = irq_chip_mask_parent,
.irq_unmask = irq_chip_unmask_parent,
.irq_ack = irq_chip_ack_parent,
- .irq_set_type = irq_chip_set_type_parent,
.irq_write_msi_msg = mvebu_icu_write_msi_msg,
.flags = IRQCHIP_SUPPORTS_LEVEL_MSI,
},
A regression was introduced in commit d929e4db22b6 ("irqchip/irq-mvebu-icu: Prepare for real per device MSI") that causes the Armada thermal driver to fail during probe with the following error: genirq: Setting trigger mode 4 for irq 85 failed (irq_chip_set_type_parent+0x0/0x34) armada_thermal f2400000.system-controller:thermal-sensor@70: Cannot request threaded IRQ 85 armada_thermal f2400000.system-controller:thermal-sensor@70: probe with driver armada_thermal failed with error -22 The issue occurs because irq_set_type is assigned to irq_chip_set_type_parent, but the parent IRQ chip does not implement the irq_set_type operation. This causes the trigger mode configuration to fail. This patch resolves the issue by removing the irq_set_type assignment. With no irq_set_type, __irq_set_trigger safely skips the trigger configuration, restoring functionality to the thermal driver. Fixes: d929e4db22b6 ("irqchip/irq-mvebu-icu: Prepare for real per device MSI") Signed-off-by: Stefan Eichenberger <eichest@gmail.com> --- drivers/irqchip/irq-mvebu-icu.c | 2 -- 1 file changed, 2 deletions(-)