regmap_init_mmio_clk(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… regmap_init_mmio_clk β€” kernel API manual, but make it cute

okay so bestie, this is regmap_init_mmio_clk(9) from the Kernel API Manual and it is literally the moment your register map gets a clock. we're doing this together, no cap.


✨ NAME ✨

regmap_init_mmio_clk β€” Initialise register map with register clock

like, it sets up your register map and it brings the register clock along for the ride πŸŽ€


🌸 SYNOPSIS 🌸

regmap_init_mmio_clk (dev , clk_id , regs , config );

that's the whole vibe. four things in, one regmap (or an error) out πŸ’–


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” Device that will be interacted with. the main character we're doing all this for πŸ‘‘
  • clk_id β€” register clock consumer ID. yes, the clock needs a name to be looked up by, iykyk ⏰
  • regs β€” Pointer to memory-mapped IO region. the actual memory-mapped real estate, mmio and all πŸ—ΊοΈ
  • config β€” Configuration for register map. all the settings, all the choices, it's giving customization ✨

πŸ’œ DESCRIPTION πŸ’œ

okay so the important bit, and I need you to hear me on this: The return value will be an ERR_PTR on error or a valid pointer to a struct regmap.

so like β€” check it. don't just assume it worked. if it's bad news it comes back as an ERR_PTR, if it's good news it's a real live struct regmap pointer 🫢

Also: this implies 'fast_io'. that's it, that's the note. it's implied. periodt πŸ’…


πŸ”₯ SEE ALSO πŸ”₯

bestie there are SO many siblings, buckle up:


lowkey the whole regmap family is iconic and this one is just the mmio + clock version. go read the rest, you'll be obsessed 🌈

that's the page!! sources say it lives in ./include/linux, dated October 2026, and it goes by regmap_init_mmio_clk(9) β€” mwah, bye bestie πŸ’‹πŸ’–

πŸ“¦ where this page comes from