fwnode_links...ge_consumers(9)
π fwnode_links_purge_consumers
okay bestie, welcome to the Kernel API Manual β yes that manual, the one with the lore π«Ά. Today's main character is fwnode_links_purge_consumers, and no, the page title being all truncated like fwnode_links...ge_consumers(9) is not a typo, that's just how the terminal chose to serve it to us. we move π.
β¨ NAME β¨
fwnode_links_purge_consumers β literally deletes every consumer link belonging to a fwnode_handle. that's the whole job. she's a cleaner, and she's booked and busy π§Ήπ
π¦ SYNOPSIS π¦
void fwnode_links_purge_consumers (struct fwnode_handle *fwnode );
returns nothing (void), takes one pointer, no cap. it's giving "small function, big responsibility" π
π ARGUMENTS π
fwnodeβ thefwnodewhose consumer links need to be deleted. that's it, that's the parameter. she's the one getting her links purged, bestie π₯
πΈ DESCRIPTION πΈ
so what does she do? fwnode_links_purge_consumers deletes all consumer links that connect directly to fwnode. not indirectly, not vibes-adjacent β directly. every single one, gone, periodt π
β¨
π SEE ALSO π
right, buckle up buttercup, because the SEE ALSO section on this page is huge β she ate and left absolutely no crumbs ππ. also worth noting: the kernel file in play here is ./drivers/base/core.c, and every one of these bad boys is a (9) kernel API page:
__fwnode_link_add(9)__fwnode_link_del(9)__fwnode_link_cycle(9)fwnode_links_purge_suppliers(9)fwnode_links_purge(9)__fwnode_links_move_consumers(9)__fw_devlink_pickup_dangling_consumers(9)fw_devlink_refresh_fwnode(9)device_is_dependent(9)device_pm_move_to_tail(9)device_link_wait_removal(9)device_link_add(9)device_link_del(9)device_link_remove(9)device_links_check_suppliers(9)__device_links_queue_sync_state(9)device_links_flush_sync_list(9)device_links_force_bind(9)device_links_driver_bound(9)__device_links_no_driver(9)device_links_no_driver(9)device_links_driver_cleanup(9)device_links_busy(9)device_links_unbind_consumers(9)device_links_purge(9)wait_for_init_devices_probe(9)fwnode_is_ancestor_of(9)fwnode_get_next_parent_dev(9)__fw_devlink_relax_cycles(9)fw_devlink_create_devlink(9)__fw_devlink_link_to_consumers(9)__fw_devlink_link_to_suppliers(9)dev_driver_string(9)device_release(9)devm_device_add_group(9)devices_kset_move_before(9)devices_kset_move_after(9)devices_kset_move_last(9)device_create_file(9)device_remove_file(9)device_remove_file_self(9)device_create_bin_file(9)device_remove_bin_file(9)device_initialize(9)kobject_has_children(9)dev_set_name(9)device_add(9)device_register(9)get_device(9)put_device(9)device_del(9)device_unregister(9)device_get_devnode(9)device_for_each_child(9)device_for_each_child_reverse(9)device_for_each_child_reverse_from(9)device_find_child(9)device_offline(9)device_online(9)__root_device_register(9)root_device_unregister(9)device_create(9)device_create_with_groups(9)device_destroy(9)device_rename(9)device_move(9)device_change_owner(9)device_shutdown(9)dev_err_probe(9)dev_warn_probe(9)set_primary_fwnode(9)set_secondary_fwnode(9)device_remove_of_node(9)device_add_of_node(9)device_set_of_node_from_dev(9)get_dev_from_fwnode(9)
like?? seventy-something cross-references?? she's connected, she knows everybody, main character energy fr fr ππ
ngl bestie, if you're deep infwnodeconsumer link territory, just go readfwnode_links_purge_suppliers(9)andfwnode_links_purge(9)next β they're right there and they're basically siblings π«Ά
okay that's the page!! sending you off with a cute little sign-off π: this one lives under ./drivers/base, it's dated October 2026, and the header/footer both spell it fwnode_links...ge_consumers(9) because the terminal simply refuses to be normal πβ¨ bye bestie, go purge some links (responsibly) ππ¦πΈ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms