driver_find_...ce_by_fwnode(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… driver_find_...ce_by_fwnode(9) β€” from the Kernel API Manual ✨

okay so bestie, listen up 🫢 this is the driver_find_...ce_by_fwnode(9) page, and honestly it's a short one but it ate. it's the device iterator you reach for when you want to find one specific device by its fwnode pointer. no cap, that's the whole vibe.


🌸 NAME 🌸

driver_find_device_by_fwnode β€” device iterator for locating a particular device by fwnode pointer.

like, it's giving "search party but make it kernel" πŸ”πŸ’–


✨ SYNOPSIS ✨

struct device * driver_find_device_by_fwnode (struct device_driver *drv
, const struct fwnode_handle *fwnode );

periodt. that's the signature, don't touch it πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • drv β€” the driver we're iterating. yup, you're walking through everything this driver has got, main character energy 🌈
  • fwnode β€” fwnode pointer to match. this is the one we're looking for, the whole reason we're here πŸ”₯

πŸ¦‹ SEE ALSO πŸ¦‹

all the siblings and cousins, iykyk:

ngl, that's a whole friend group and they're all iconic πŸ‘‘


lowkey reminder: this page is literally just the lookup-by-fwnode one β€” the other finders above are separate pages, so don't come for me if you wanted one of those πŸ’€

and that's the page, bestie! πŸ“ source/version: ./include/linux/device, dated October 2026, and yes it's still filed under driver_find_...ce_by_fwnode(9) β€” slay, go read your kernel headers πŸ’–βœ¨πŸ§š

πŸ“¦ where this page comes from