of_irq_find_parent(9)

🎀 of_irq_find_parent(9) 🎀

okay bestie, we're in the Kernel API Manual and this one is literally about finding a device node's interrupt parent node. no cap, it's giving "where's my parent" energy. 💅✨

🌸 NAME 🌸

of_irq_find_parent — given a device node, find its interrupt parent node. 🦋💖

✨ SYNOPSIS ✨

struct device_node * of_irq_find_parent (struct device_node *child );

💖 ARGUMENTS 💖

• child — pointer to device node. that's the node you're asking about, bestie 🫶

🔥 RETURN 🔥

A pointer to the interrupt parent node with refcount increased, or NULL if the interrupt parent could not be determined. 💀 so yeah, NULL is the "couldn't figure it out" vibe.

👑 SEE ALSO 👑

Kernel file ./drivers/of/irq.c, plus these iconic little references:

• irq_of_parse_and_map(9)
• of_irq_parse_raw(9)
• of_irq_parse_one(9)
• of_irq_to_resource(9)
• of_irq_get(9)
• of_irq_get_byname(9)
• of_irq_count(9)
• of_irq_to_resource_table(9)
• of_irq_init(9)
• of_msi_xlate(9)
• of_msi_map_get_device_domain(9)
• of_msi_get_domain(9)
• of_msi_configure(9)

that's the whole vibe 💜 shoutout to the footer besties: source/version ./drivers/of and date October 2026, with of_irq_find_parent(9) living her best life. mwah 💋🎀