fwnode_irq_get_byname(9)

🌸 fwnode_irq_get_byname(9) 🌸

okay so bestie, welcome to the Kernel API Manual — this one's a kernel function page and it's genuinely so useful, i promise. it's giving "i just need my IRQ number and i need it now" energy. let's get into it 💅

---

✨ NAME ✨

fwnode_irq_get_byname — Get IRQ from a fwnode using its name

like, you hand it a name and it hands you an IRQ. simple as that, no cap 🫶

---

✨ SYNOPSIS ✨

int fwnode_irq_get_byname (const struct fwnode_handle *fwnode , const
char *name );

---

✨ ARGUMENTS ✨

• fwnode — Pointer to the firmware node. yeah, this is the thing you're searching in 🎀
• name — IRQ name. the string you're hunting for, bestie 🔍

---

✨ DESCRIPTION ✨

okay so here's the vibe: it finds a match to the string name in the 'interrupt-names' string array in _DSD for ACPI, or in of_node for Device Tree. (two different worlds, one function, we love a bilingual icon 👑)

then — and this is the main character moment — it gets the Linux IRQ number of the IRQ resource corresponding to the index of the matched string. so the position of your name in that array is literally the whole plot. iykyk ✨

---

✨ RETURN ✨

Linux IRQ number on success 🎉 — or a negative errno otherwise 😭 (so like, always check, fr fr)

---

✨ SEE ALSO ✨

Kernel file ./drivers/base/property.c, plus the whole friend group:

• device_property_present(9)
• fwnode_property_present(9)
• device_property_read_bool(9)
• fwnode_property_read_bool(9)
• device_property_read_u8_array(9)
• device_property_read_u16_array(9)
• device_property_read_u32_array(9)
• device_property_read_u64_array(9)
• device_property_read_string_array(9)
• device_property_read_string(9)
• device_property_match_string(9)
• fwnode_property_read_u8_array(9)
• fwnode_property_read_u16_array(9)
• fwnode_property_read_u32_array(9)
• fwnode_property_read_u64_array(9)
• fwnode_property_read_string_array(9)
• fwnode_property_read_string(9)
• fwnode_property_match_string(9)
• fwnode_property_match_property_string(9)
• fwnode_property_get_reference_args(9)
• fwnode_find_reference(9)
• fwnode_get_name(9)
• fwnode_get_name_prefix(9)
• fwnode_name_eq(9)
• fwnode_get_parent(9)
• fwnode_get_next_parent(9)
• fwnode_count_parents(9)
• fwnode_get_nth_parent(9)
• fwnode_get_next_child_node(9)
• fwnode_get_next_available_child_node(9)
• device_get_next_child_node(9)
• fwnode_get_named_child_node(9)
• device_get_named_child_node(9)
• fwnode_handle_get(9)
• fwnode_device_is_available(9)
• fwnode_get_child_node_count(9)
• fwnode_get_named_child_node_count(9)
• fwnode_get_phy_mode(9)
• device_get_phy_mode(9)
• fwnode_iomap(9)
• fwnode_irq_get(9)
• fwnode_graph_get_next_endpoint(9)
• fwnode_graph_get_port_parent(9)
• fwnode_graph_get_remote_port_parent(9)
• fwnode_graph_get_remote_port(9)
• fwnode_graph_get_remote_endpoint(9)
• fwnode_graph_get_endpoint_by_id(9)
• fwnode_graph_get_endpoint_count(9)
• fwnode_graph_parse_endpoint(9)
• fwnode_connection_find_match(9)
• fwnode_connection_find_matches(9)

that's a lot of siblings and honestly? iconic. go read them all, i'll wait 💜

---

lowkey a tip: this page lives under ./drivers/base, and the whole thing is dated October 2026. if you're citing it in a bug report, that's your receipt 🧾✨

okay that's the whole page bestie, slay, go get your IRQ 🎀💖🌟 — fwnode_irq_get_byname(9), from the Kernel API Manual, ./drivers/base, October 2026. periodt. 💅