The RISC-V APLIC interrupt controller driver is a regular platform
driver so we need to ensure that it is probed as soon as possible.
To achieve this, we mark the interrupt controller device nodes with
FWNODE_FLAG_BEST_EFFORT (just like console DT node).
Fixes: 8f486cab263c ("driver core: fw_devlink: Allow firmware to mark devices as best effort")
Signed-off-by: Anup Patel <apatel@xxxxxxxxxxxxxxxx>
---
drivers/of/irq.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/of/irq.c b/drivers/of/irq.c
index 174900072c18..94e1d9245cff 100644
--- a/drivers/of/irq.c
+++ b/drivers/of/irq.c
@@ -535,6 +535,16 @@ void __init of_irq_init(const struct of_device_id *matches)
INIT_LIST_HEAD(&intc_desc_list);
INIT_LIST_HEAD(&intc_parent_list);
+ /*
+ * We need interrupt controller platform drivers to work as soon
+ * as possible so mark the interrupt controller device nodes with
+ * FWNODE_FLAG_BEST_EFFORT so that fw_delink knows not to delay
+ * the probe of the interrupt controller device for suppliers
+ * without drivers.
+ */
+ for_each_node_with_property(np, "interrupt-controller")
+ np->fwnode.flags |= FWNODE_FLAG_BEST_EFFORT;
+
for_each_matching_node_and_match(np, matches, &match) {
if (!of_property_read_bool(np, "interrupt-controller") ||
!of_device_is_available(np))
--
2.34.1
