device_property_read_bool(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– device_property_read_bool(9) πŸ’–

ok so bestie, buckle up β€” this is a page from the Kernel API Manual, and it's literally about asking a device "hey, is this property a yes or a no?" πŸŽ€


✨ NAME ✨

device_property_read_bool β€” returns the value for a boolean property of a device. that's it. that's the whole vibe. 🌸


πŸ¦‹ SYNOPSIS πŸ¦‹

bool device_property_read_bool (const struct device *dev , const char *propname );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the device whose property you're checking, bestie. the main character of this whole operation πŸ’…
  • propname β€” the name of the property. you gotta tell it which one you're asking about 🏷️

πŸ’« DESCRIPTION πŸ’«

ngl, the description here is short and sweet: use device_property_present to check for the property presence. that's literally the whole note 😭 β€” so like, if you're wondering whether the property is even there before you go asking what it says, device_property_present is your girl. 🫢


πŸ”₯ RETURN πŸ”₯

it returns whether the property propname is true or false in the device firmware description. like, yes or no, binary, iconic behaviour ⭐


πŸ‘‘ SEE ALSO πŸ‘‘

ok this list is long β€” it's giving "she listed everyone at the function in her close friends story" πŸ’€ but we're listing them ALL because every single one matters, no cap:

Kernel file ./drivers/base/property.c, plus:

device_property_present(9), fwnode_property_present(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_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)


reminder bestie: this page lives under ./drivers/base in the kernel tree, and it's dated October 2026 β€” so mark your calendar πŸ—“οΈβœ¨

and that's the whole page!! stay hydrated, read your booleans, and slay πŸ’…πŸ¦‹πŸ’–

πŸ“¦ where this page comes from