fwnode_device_is_available(9)

💖 fwnode_device_is_available — the kernel API manual, bestie edition 💖

okay so real talk, this is fwnode_device_is_available(9) from the Kernel API Manual and it's genuinely one of the chillest little functions you'll ever meet. no cap. let me put you on. ✨

---

🎀 NAME 🎀

fwnode_device_is_available — check if a device is available for use, that's literally it, that's the whole job 💅

---

✨ SYNOPSIS ✨

bool fwnode_device_is_available (const struct fwnode_handle *fwnode );

like look at her. one argument. returns a bool. icon behavior honestly 🫶

---

🌸 ARGUMENTS 🌸

• fwnode — Pointer to the fwnode of the device. that's the thing you're vibe-checking, bestie 🦋

---

⭐ RETURN ⭐

returns true if the device is available for use. otherwise? returns false. that's the whole plot, no twists 🔥

---

💜 DESCRIPTION 💜

so here's the tea ☕ — for fwnode node types that don't implement the .device_is_available operation, this function returns true.

like. it doesn't have an opinion, so it just says yes by default. main character energy of the highest order tbh 😭 the way that it's just gonna assume available unless someone actually implements the check?? love that for us 💀

not me memorizing this: no .device_is_available implementation = automatic true. periodt.

---

🦋 SEE ALSO 🦋

buckle up bestie, this list is LONG and every single one of these is iconic in her own right 👑

• 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_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_irq_get_byname(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)

also the kernel file lives at ./drivers/base/property.c if you wanna go read the source yourself, iykyk 📖🧚

---

🌈 the sign-off 🌈

that's the whole page bestie!! this one came from ./drivers/base, dated October 2026, and it's the fwnode_device_is_available(9) page through and through. go forth and check your devices, you absolute legend 👑💖✨