davinci_lpsc_clk_register(9)

💅 davinci_lpsc_clk_register(9) — the Kernel API Manual, bestie edition 🎀

okay so picture this: you're deep in davinci_lpsc_clk_register from the Kernel API Manual (section 9, kernel-space girlies only 💖) and you just need to register an LPSC clock. that's it. that's the whole vibe. no cap, the name literally says it: register LPSC clock. iconic behavior tbh 🌸

✨ SYNOPSIS ✨

struct davinci_lpsc_clk * davinci_lpsc_clk_register (struct device *dev
, const char *name , const char *parent_name , struct regmap *regmap ,
u32 md , u32 pd , u32 flags );

seven arguments, one struct pointer back, and honestly? she ate 🔥

🫶 ARGUMENTS 🫶

• dev — the clock's device, or NULL if you're feeling mysterious and unmoored 🙈 literally either one is fine bestie.
• name — name of this clock. give her a good one, she deserves it ⭐
• parent_name — name of clock's parent. yes she has a mother 👑
• regmap — the PSC MMIO region. this is where the actual hardware lives, treat her with respect 💜
• md — local PSC number. a u32, not a vibe check, keep it straight 🔢
• pd — power domain. also a u32. the domain of power 💅
• flags — the LPSC_* flags. she's flexible, she's got options, she's a u32 too ✨

🦋 SEE ALSO 🦋

• Kernel file ./drivers/clk/davinci/psc.c — the source, go read her 📖
• struct davinci_lpsc_clk(9) — the struct herself, main character energy fr fr 👑
• best_dev_name(9) — the helper bestie you'll also wanna know 🌈

heads up: if you pass NULL for dev that's allowed, but everything else is you doing the work, so know your regmap and your flags before you call her 🍓

and that's the page!! 💀 shoutout to ./drivers/clk/davinci for hosting the files, October 2026 for the timestamp, and davinci_lpsc_clk_register(9) for being the whole point of this document 🧚 mwah, go register some clocks, iykyk 💖🎀