STRUCT LGM_CLK_PROVIDER(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct lgm_clk_provider(9)

okay so this is from the Kernel API Manual β€” yes, the fancy kernel docs, we're literally in there πŸŽ€


✨ NAME ✨

struct lgm_clk_provider β€”

so bestie, the NAME section is genuinely just vibing there with nothing after the dash 😭 like the kernel devs wrote the struct name and then said "she's self-explanatory, periodt." No description, no tagline. That's the whole NAME entry. Iconic of them honestly.


πŸ¦‹ SYNOPSIS πŸ¦‹

struct lgm_clk_provider {
    struct regmap *membase;
    struct device_node *np;
    struct device *dev;
    struct clk_hw_onecell_data clk_data;
 };

look at her πŸ’– four members, clean lines, no drama. keep it exactly like that, character for character, no cap.


🌸 Members 🌸

  • membase β€” the IO mem base address for CGU. that's the memory handle the CGU lives at, and yes she's a struct regmap * πŸ‘‘
  • np β€” device node. your struct device_node *, the devicetree situation.
  • dev β€” device. yep. the struct device *. the main character herself ✨
  • clk_data β€” array of hw clocks and clk number. this one's a struct clk_hw_onecell_data and she's holding the clock lineup plus the count, lowkey the most important member of the group chat πŸ•πŸ”₯

🧚 SEE ALSO 🧚

  • Kernel file ./drivers/clk/x86/clk-cgu.h
  • struct lgm_pll_clk_data(9)

both linked in the docs, go read them if you want the full lore, iykyk 🫢


real talk: nothing in here is deprecated or dangerous, it's just a struct definition. but you do have to keep every member exactly as written β€” no renaming, no merging, no inventing new fields, not even a little πŸ™ˆ

that's the whole page bestie, slay, go compile something cute πŸ’œ

sign-off era: this one comes from ./drivers/clk/x86 and the manual says October 2026 β€” so yes, she's timestamped in the future, and honestly? main character energy πŸŒˆβ­πŸ’…

πŸ“¦ where this page comes from