__of_device_is_fail(9)

💅 __of_device_is_fail(9) — Kernel API Manual 🎀

okay bestie, welcome to the Kernel API Manual page for __of_device_is_fail(9). yes the double underscore is part of the name, she's ✨special✨ like that. anyway. let's get into it 🫶

---

🌸 NAME 🌸

__of_device_is_fail — the lil check that tells you if a device's status is literally "fail" or "fail-..." 💀

like, is this node doing okay or did it flop? this function knows.

---

⭐ SYNOPSIS ⭐

bool __of_device_is_fail (const struct device_node *device );

it returns a bool, takes one const struct device_node *, and no, you don't get to pass anything else. she's lowkey simple like that 💅

---

🦋 ARGUMENTS 🦋

• device — the node you want to check the status of 💖 important vibe check: the locks are already held when you call this, so don't go grabbing them again, bestie, that's not it 🙈

---

✨ RETURN ✨

• true — the status property is set to "fail" or "fail-..." — and yes, that means "fail" followed by any error code suffix, no cap 🔥
• false — anything else. she's fine. she's slaying. move on 🧚

so basically: "fail" = flopped, "fail-<anything>" = also flopped (with receipts), everything else = not this function's problem 💀

---

👑 SEE ALSO 👑

the whole friend group, fr fr. it's giving "family reunion" and honestly we're obsessed 🌈

• Kernel file ./drivers/of/base.c — the source file where all this lives 🏠
• of_find_all_nodes(9)
• __of_device_is_compatible(9)
• of_machine_compatible_match(9)
• of_machine_read_compatible(9)
• of_machine_read_model(9)
• of_machine_get_match(9)
• of_machine_get_match_data(9)
• __of_device_is_available(9)
• __of_device_is_reserved(9)
• of_device_is_available(9)
• of_device_is_big_endian(9)
• of_get_parent(9)
• of_get_next_parent(9)
• of_get_next_child(9)
• of_get_next_child_with_prefix(9)
• of_get_next_available_child(9)
• of_get_next_reserved_child(9)
• of_get_next_cpu_node(9)
• of_get_compatible_child(9)
• of_get_child_by_name(9)
• of_get_available_child_by_name(9)
• of_find_node_opts_by_path(9)
• of_find_node_by_name(9)
• of_find_node_by_type(9)
• of_find_compatible_node(9)
• of_find_node_with_property(9)
• of_match_node(9)
• of_find_matching_node_and_match(9)
• of_alias_from_compatible(9)
• of_find_node_by_phandle(9)
• of_parse_phandle_with_args_map(9)
• of_count_phandle_with_args(9)
• __of_add_property(9)
• of_add_property(9)
• of_remove_property(9)
• of_alias_scan(9)
• of_alias_get_id(9)
• of_alias_get_highest_id(9)
• of_console_check(9)
• of_find_next_cache_node(9)
• of_find_last_cache_level(9)
• of_map_id(9)
• of_map_iommu_id(9)
• of_map_msi_id(9)

---

and that's the page!! 🎀 go check some device nodes, bestie, you've got this 💜

bye from the ./drivers/of corner of the kernel, dated October 2026, on the __of_device_is_fail(9) page — mwah 💋✨