STRUCT LGM_CLK_PROVIDER(9)
π 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 astruct regmap *πnpβ device node. yourstruct device_node *, the devicetree situation.devβ device. yep. thestruct device *. the main character herself β¨clk_dataβ array of hw clocks and clk number. this one's astruct clk_hw_onecell_dataand 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms