__of_device_is_reserved(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ __of_device_is_reserved(9) β€” straight out of the Kernel API Manual

okay bestie, listen, this one's a tiny little function from the kernel's device tree world and honestly it's giving "small but mighty" πŸ’… we're literally just checking one thing and dipping. no cap.


✨ NAME ✨

__of_device_is_reserved β€” check if a device is reserved πŸŽ€


🌸 SYNOPSIS 🌸

bool __of_device_is_reserved (const struct device_node *device );

like, that's the whole vibe. returns a bool, takes one const struct device_node *. clean. iconic. no notes. ✨


πŸ’– ARGUMENTS πŸ’–

  • device β€” the node you're checking for availability, okay? and heads up bestie, this one expects the locks to already be held when you call it 🫢 so like… you handle the locks, this function handles the check. division of labor, we love to see it.

πŸ‘‘ RETURN πŸ‘‘

  • true if the status property is set to "reserved" πŸ’€
  • false otherwise

that's it. that's the whole answer. binary queen behavior, honestly. πŸ”₯

lowkey important: this is the version that assumes the locks are held. don't forget that part, bestie, fr fr.

🧚 SEE ALSO 🧚

sooo there's a whole friend group here. first up, the kernel file it lives in:

  • Kernel file ./drivers/of/base.c

and then the entire of-crew, in the order the manpage gives them πŸŽ€:


and that's the whole page, bestie β€” go check some reserved devices πŸ’œ

sign-off time πŸŽ€ this one ships as part of the Kernel API Manual, lives in ./drivers/of, and the date on it is October 2026. periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from