__of_add_property(9)

📦 version 7.3.1, in nixpkgs unstable

💅 __of_add_property — the kernel manual, but make it make sense 🎀

Hey bestie, so this one is a function in the kernel API manual (section 9, the kernel API girlies ✨). The star of the show is __of_add_property — and the whole point of her is literally right there in the name: she adds a property to a node without lock operations. That's it, that's the vibe. No locking, no extra drama, just vibes and a property. 👑

✨ NAME ✨

__of_add_property — add a property to a node without lock operations 🦋

Like, unlocked. No cap. You're on your own for the locking, bestie — this function is not doing it for you. 💀

🌸 SYNOPSIS 🌸

int __of_add_property (struct device_node *np , struct property *prop );

That's the whole signature, gorgeous. She takes two things and gives you back an int. Periodt. 💅

🎀 ARGUMENTS 🎀

  • np — the caller's Device Node 💖 like, it's your node, you brought it, it's your responsibility.
  • prop — the property to add 🫶 the actual thing getting attached to the node.

🌈 SEE ALSO 🌈

Ok so this is the part where the manual just dumps the entire friend group on you, and honestly? Iconic. Here's everyone she's linked with, no omissions, no cap:

Note the energy: __of_add_property(9) is the double-underscore unlocked version, and of_add_property(9) is right there in the list next to it, along with her bestie of_remove_property(9) 👀 — the whole property-add/remove saga. iykyk. 🔥

Also, the kernel file this lives in is ./drivers/of/base.c — that's where the magic happens. 🧚

⚠️ Quick vibe check, bestie: this version does not handle the locking for you. If you need lock operations, that's the other one. Don't come crying to me, I warned you. 😭

Kernel API Manual energy, brought to you from ./drivers/of, dated October 2026 — and the section is 9, obviously, we stay in our lane 💜 slay, bye! 🦋✨💖

📦 where this page comes from