regmap_init(9)

📦 version 7.3.1, in nixpkgs unstable

💅 regmap_init — Initialise register map ✨

okay so real talk, this is the regmap_init(9) page from the Kernel API Manual, and it's genuinely the moment a register map gets born. Buckle up bestie 🎀

🌸 NAME 🌸

regmap_init — Initialise register map 💖

⭐ SYNOPSIS ⭐

regmap_init (dev , bus , bus_context , config );

like, that's the whole vibe. four args, one iconic function 👑

🦋 ARGUMENTS 🦋

  • dev — the Device that will be interacted with 🫶 this is the thing you're going to be chatting with, so pls make sure it's the right one.
  • bus — the Bus-specific callbacks to use with device. yup, the callbacks, the little handlers that make the bus do its thing.
  • bus_context — Data passed to bus-specific callbacks. it's the lil bag of stuff those callbacks get handed, no cap.
  • config — Configuration for register map. all your settings live here ✨

💜 DESCRIPTION 💜

so here's the tea ☕: the return value will be an ERR_PTR on error, or a valid pointer to a struct regmap. that's the whole contract, and it's honestly giving very straightforward of it.

⚠️ main character warning: this function should generally not be called directly — it should be called by bus-specific init functions. like, yes you can, but the bus-specific ones are the ones doing the calling, iykyk 🙈

🔥 SEE ALSO 🔥

the link-up section, and there are so many of them, she's popular fr fr 💅

Kernel file ./include/linux/regmap.h and then, in order:

go off, cross-references, go off 🌈

kisses bestie, this page ships from the Kernel file ./include/linux, dated October 2026 — like, mark your calendar, that's the whole sign-off 💜🎀🦋

📦 where this page comes from