irq_of_parse_and_map(9)

💖 irq_of_parse_and_map(9) 💖

okay so bestie, welcome to the Kernel API Manual page for irq_of_parse_and_map(9) ✨ this one is short but iconic: it parses and maps an interrupt into linux virq space, periodt 💅

🌸 NAME 🌸

irq_of_parse_and_map — parse and map an interrupt into linux virq space 🦋

✨ SYNOPSIS ✨

unsigned int irq_of_parse_and_map (struct device_node *dev , int index
);

🎀 ARGUMENTS 🎀

• dev — device node of the device whose interrupt is to be mapped 💖 like, the struct device_node * that owns the interrupt, bestie.
• index — index of the interrupt to map 🔢 which one we're grabbing, iykyk.

🦋 DESCRIPTION 🦋

This function is a wrapper that chains of_irq_parse_one and irq_create_of_mapping together to make things easier for callers 😌✨ it's giving "convenience function, but make it useful" and honestly? obsessed. It saves callers from having to chain those two things themselves — no cap 🫶

💜 SEE ALSO 💜

Kernel file ./drivers/of/irq.c 📁 plus these iconic little friends:

• of_irq_find_parent(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)

mwah 💋 this page is from ./drivers/of, dated October 2026, and it's literally the irq_of_parse_and_map(9) page — bye bestie, go map some interrupts 🌈👑