altr_sysmgr_...p_by_phandle(9)

📦 version 7.3.1, in nixpkgs unstable

💅 altr_sysmgr_...p_by_phandle(9) — a Kernel API Manual moment

okay so bestie, welcome to the group chat. this is a page from the Kernel API Manual, and the star of the show is altr_sysmgr_...p_by_phandle(9). yes the name is a whole mouthful, no i will not be shortening it, it's iconic as-is 🎀

✨ NAME ✨

altr_sysmgr_regmap_lookup_by_phandle — and honestly the original page just trails off after the dash with zero description, so like… that's the vibe. it exists. that's the whole name section. 💀

🌸 SYNOPSIS 🌸

struct regmap * altr_sysmgr_regmap_lookup_by_phandle (struct device_node
*np , const char *property );

literally right there. it hands you back a struct regmap *, and you feed it a struct device_node pointer plus a property name string. slay.

🦋 ARGUMENTS 🦋

  • np — a Pointer to the device's Device Tree node. that's your starting point, bestie, the node in question 🫶
  • property — the Device Tree property name which references the sysmgr. yes, it's the string that points at the sysmgr, no cap.

💖 DESCRIPTION 💖

so what does it actually do? it Finds the sysmgr previous configured in probe and returns the regmap property. that's it. that's the whole mission. it goes looking, it finds, it returns. main character energy tbh ✨

⭐ RETURN ⭐

  • regmap if found 🔥
  • or an error if not found 😭

like, you either get the goods or you get the error. vibe check either way.

🌈 SEE ALSO 🌈

go read those next, iykyk 💜

lowkey reminder before you go: those related pages are struct altr_sysmgr(9), s10_protected_reg_write(9) and s10_protected_reg_read(9), and the source file is ./drivers/mfd/altera-sysmgr.c. keep the names exact when you go look them up, bestie, no inventing 💅

and that's a wrap, gorgeous 🧚 this little adventure came from the ./drivers/mfd corner of the world, dated October 2026, version pinned to that very same altr_sysmgr_...p_by_phandle(9) manual header. bye bestie, drink some water, man pages await 🍓👑

📦 where this page comes from