devm_regmap_init_mmio_clk(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… devm_regmap_init_mmio_clk β€” Kernel API Manual ✨

okay so bestie, we're in the Kernel API Manual today and this little cutie is called devm_regmap_init_mmio_clk. it's giving "managed register map, but make it clock-aware" πŸ•°οΈ and honestly? iconic.


🌸 NAME

devm_regmap_init_mmio_clk β€” Initialise managed register map with clock πŸ’–

like, it sets up your regmap, it's managed (so nobody has to hand-free it), and there's a clock involved. slay.


✨ SYNOPSIS

devm_regmap_init_mmio_clk (dev , clk_id , regs , config );

that's the whole vibe check right there β€” four args, no cap.


πŸŽ€ ARGUMENTS

  • dev β€” the Device that will be interacted with. your main character device, fr fr 🫢
  • clk_id β€” the register clock consumer ID. that's how you tell it which clock is your clock πŸ•°οΈ
  • regs β€” a Pointer to memory-mapped IO region. the actual memory real estate, lowkey the whole point πŸ—ΊοΈ
  • config β€” Configuration for register map. all the settings, all the vibes βš™οΈ

πŸ¦‹ DESCRIPTION

so here's the tea: the return value will be an ERR_PTR on error, or a valid pointer to a struct regmap πŸ’–. you gotta check it, bestie β€” do not just assume it worked, that's not the energy we're bringing πŸ”₯.

the regmap will be automatically freed by the device management code ✨ β€” that's the "devm" part, that's the whole managed moment, you literally don't have to lift a finger πŸ’….

and it Implies 'fast_io' πŸ‘‘. yes queen, fast io is baked in.


🌈 SEE ALSO

grab a snack, this list is long and we're getting through all of it πŸ“:

Kernel file ./include/linux/regmap.h 🧚, plus:

like I said. long list. we ate though πŸ’…


okay that's the whole page bestie!! πŸ’œ this one lives in ./include/linux (the Kernel API Manual fam 🫢), it's dated October 2026 ⭐, and the page itself is devm_regmap_init_mmio_clk(9) β€” go forth and initialise those managed register maps responsibly, mwah πŸ’–πŸŽ€

πŸ“¦ where this page comes from