of_syscon_register_regmap(9)

📦 version 7.3.1, in nixpkgs unstable

💅 of_syscon_register_regmap(9) 💅

okay so bestie, welcome to the of_syscon_register_regmap(9) page — it's a kernel API manual, it's short, it's iconic, and it's about to be your new fave little helper ✨

🎀 NAME 🎀

of_syscon_register_regmap — literally just: register a regmap for the device node you specified 🫶

🌸 SYNOPSIS 🌸

int of_syscon_register_regmap (struct device_node *np , struct regmap *regmap );

like. that's the whole vibe. two args, one int back. no cap 💅

🦋 ARGUMENTS 🦋

  • np — the device tree node, bestie. the DT node in question 🌳
  • regmap — a pointer to the regmap object ✨ (yes, a pointer, we're being fancy)

💖 DESCRIPTION 💖

so here's the tea, okay? this function registers an externally created regmap object with syscon, for the device tree node you hand it. like, you made the regmap somewhere else and now you're introducing it to syscon. networking, but for kernel data structures 🧚

and then — and this is the main character moment — that regmap gets returned to client drivers via the syscon_regmap_lookup_by_phandle API. so everyone who looks it up by phandle gets your regmap. slay. it's giving matchmaker energy 💜

🔥 RETURN 🔥

  • 0 on success 🎉 (we love a zero)
  • a negative error code on failure 💀 (read it, don't ignore it, i'm begging)

⭐ SEE ALSO ⭐

go read those too, iykyk 📚

ngl bestie, if the lookup isn't giving what you expected, double-check that you actually registered the regmap for the right node before you start blaming the kernel 🙈

okay that's the whole page, no notes 💅 this adorable little manual lives at ./drivers/mfd, dated October 2026, and it's titled of_syscon_register_regmap(9) — drink water, recompile clean, mwah 🍓🌈💜

📦 where this page comes from