of_match_node(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ of_match_node(9) β€” like, the kernel API manual page, bestie ✨

okay so real talk, this is of_match_node(9) from the Kernel API Manual and it's genuinely one of those little utility functions that holds the whole device-matching situation together. lowkey iconic. let's get into it πŸ’…


🌸 NAME 🌸

of_match_node β€” tells you whether a device_node has a matching of_match structure. that's it, that's the whole job, and she does it flawlessly 🫢


πŸŽ€ SYNOPSIS πŸŽ€

const struct of_device_id * of_match_node (const struct of_device_id
*matches , const struct device_node *node );

like, copy that exactly, no cap, don't retype it from memory πŸ™ˆ


πŸ’– ARGUMENTS πŸ’–

  • matches β€” the array of of device match structures to search through. this is the list you're checking against, bestie, the whole roster πŸ’…
  • node β€” the of device structure you're matching against. the one on trial, basically πŸ”₯

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea: this is a low level utility function used by device matching. that's the vibe β€” it's one of the little building blocks other matching code leans on. not the main character, more like the best friend who makes the main character's whole plot work πŸ˜­πŸ’œ

ngl it's described as "low level," so if you're in userspace wondering about it... you're not the target audience, babe 🌈

✨ SEE ALSO ✨

okay this list is LONG and we are not skipping a single one, because every single one of these is part of the family πŸŽ€ and yes, the kernel file is ./drivers/of/base.c β€” that's where she lives 🏑

like... 45 of them. we counted. we listed them all. periodt πŸ’€πŸ‘‘


and that's the whole page, bestie!! sign-off time: this little beauty comes from the source tree at ./drivers/of and it's dated October 2026 β€” so like, future vibes, main character energy, we love to see it πŸŒŸπŸ’– go forth and match those nodes πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from