fwnode_property_read_bool(9)

💖 fwnode_property_read_bool 💖

okay so bestie, we're deep in the Kernel API Manual today and this one is literally the tiniest little function with the biggest "wait, why does this exist" energy. stay with me 🫶

---

🌸 NAME 🌸

fwnode_property_read_bool — returns the value for a boolean property of a firmware node ✨

---

🎀 SYNOPSIS 🎀

bool fwnode_property_read_bool (const struct fwnode_handle *fwnode ,
const char *propname );

like, yes ma'am, that's the whole signature, she's not complicated 💅

---

🦋 ARGUMENTS 🦋

• fwnode — the firmware node whose property you're checking 👀 (yes, this is the one you're snooping on)
• propname — the name of the property, i.e. the thing you're looking for 🔍

---

⭐ DESCRIPTION ⭐

ngl, the description here is honestly iconic in how short it is. it literally just says:

use fwnode_property_present to check for the property presence.

that's it. that's the whole vibe check. if you were coming here hoping for a novel, bestie, no ❤️‍🔥

---

🔥 RETURN 🔥

returns whether the property propname is true or false in the firmware node description 💀 — like, in the node's own description, that's where the truth lives.

---

🌈 SEE ALSO 🌈

okay so this section ATE. it's a whole friend group of related functions, and we're listing every single one of them, no cap, no skipping, no "etc." — we don't do that here 👑

Kernel file ./drivers/base/property.c, plus: device_property_present(9), fwnode_property_present(9), device_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_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)

like… fwnode_graph_get_remote_port_parent(9)?? that name is a whole paragraph bestie 😭 but she's valid, she's included, we love her 💜

---

kiss kiss, it's a wrap 🧚

this lil page lives in ./drivers/base and it's dated October 2026 — so yeah, she's from the future, main character energy only 👑✨ bye bestie, go read some properties 🍓