fdt_getprop_namelen(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so you're on the fdt_getprop_namelen(9) page from the Kernel API Manual, and it's literally about grabbing a property value based on a substring πŸ’– bestie, let's go.


πŸ’– NAME πŸ’–

fdt_getprop_namelen β€” get property value based on substring ✨


✨ SYNOPSIS ✨

the signature is right here, no cap:

const void * fdt_getprop_namelen (const void *fdt , int nodeoffset ,
const char *name , int namelen , int *lenp );

πŸŽ€ ARGUMENTS πŸŽ€

  • fdt β€” pointer to the device tree blob 🌳
  • nodeoffset β€” offset of the node whose property to find πŸ”
  • name β€” name of the property to find 🏷️
  • namelen β€” number of characters of name to consider βœ‚οΈ
  • lenp β€” pointer to an integer variable (will be overwritten) or NULL πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

it's identical to fdt_getprop, but it only examines the first namelen characters of name for matching the property name. substring-match era, periodt πŸ’…


🌸 RETURN 🌸

pointer to the property's value or NULL on error 🫢


πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file is ./scripts/dtc/libfdt/libfdt.h β€” and here's the whole SEE ALSO squad, all together now, no omissions bestie:

fdt_offset_ptr(9), fdt_next_tag(9), fdt_first_subnode(9), fdt_next_subnode(9),
fdt_for_each_subnode(9), fdt_header_size(9), fdt_header_size_(9),
fdt_check_header(9), fdt_move(9), fdt_check_full(9), fdt_get_string(9),
fdt_string(9), fdt_find_max_phandle(9), fdt_get_max_phandle(9),
fdt_generate_phandle(9), fdt_num_mem_rsv(9), fdt_get_mem_rsv(9),
fdt_subnode_offset_namelen(9), fdt_subnode_offset(9),
fdt_path_offset_namelen(9), fdt_path_offset(9), fdt_get_name(9),
fdt_first_property_offset(9), fdt_next_property_offset(9),
fdt_for_each_property_offset(9), fdt_get_property_by_offset(9),
fdt_get_property_namelen(9), fdt_get_property(9),
fdt_getprop_by_offset(9), fdt_getprop(9), fdt_get_phandle(9),
fdt_get_alias_namelen(9), fdt_get_alias(9), fdt_get_symbol_namelen(9),
fdt_get_symbol(9), fdt_get_path(9), fdt_supernode_atdepth_offset(9),
fdt_node_depth(9), fdt_parent_offset(9),
fdt_node_offset_by_prop_value(9), fdt_node_offset_by_phandle(9),
fdt_node_check_compatible(9), fdt_node_offset_by_compatible(9),
fdt_stringlist_contains(9), fdt_stringlist_count(9),
fdt_stringlist_search(9), fdt_stringlist_get(9), FDT_MAX_NCELLS(9),
fdt_address_cells(9), fdt_size_cells(9),
fdt_setprop_inplace_namelen_partial(9), fdt_setprop_inplace(9),
fdt_setprop_inplace_u32(9), fdt_setprop_inplace_u64(9),
fdt_setprop_inplace_cell(9), fdt_nop_property(9), fdt_nop_node(9),
fdt_create_with_flags(9), fdt_create(9), fdt_resize(9),
fdt_add_reservemap_entry(9), fdt_finish_reservemap(9),
fdt_begin_node(9), fdt_property(9), fdt_property_placeholder(9),
fdt_end_node(9), fdt_finish(9), fdt_create_empty_tree(9),
fdt_open_into(9), fdt_pack(9), fdt_add_mem_rsv(9), fdt_del_mem_rsv(9),
fdt_set_name(9), fdt_setprop_namelen(9), fdt_setprop(9),
fdt_setprop_placeholder_namelen(9), fdt_setprop_placeholder(9),
fdt_setprop_u32(9), fdt_setprop_u64(9), fdt_setprop_cell(9),
fdt_setprop_string(9), fdt_setprop_namelen_string(9),
fdt_setprop_empty(9), fdt_appendprop(9), fdt_appendprop_u32(9),
fdt_appendprop_u64(9), fdt_appendprop_cell(9), fdt_appendprop_string(9),
fdt_appendprop_addrrange(9), fdt_delprop(9), fdt_add_subnode_namelen(9),
fdt_add_subnode(9), fdt_del_node(9), fdt_overlay_apply(9),
fdt_overlay_target_offset(9), fdt_strerror(9)

made with love from ./scripts/dtc/libfdt, dated October 2026, and this has been fdt_getprop_namelen(9) β€” bye bestie! πŸ«ΆπŸ’…πŸŒˆ

πŸ“¦ where this page comes from