cm_register(9)

💖 cm_register(9) 💖

okay bestie, welcome to the Kernel API Manual — this is the page for cm_register(9), and it's lowkey iconic because it's all about handing the OMAP CM common interface the per-SoC low-level data it needs. ✨

🌸 NAME 🌸

• cm_register — register per-SoC low-level data with the CM.

💅 SYNOPSIS 💅

int cm_register (const struct cm_ll_data *cld );

🎀 ARGUMENTS 🎀

• cld — low-level per-SoC OMAP CM data & function pointers to register. That's the whole vibe: you pass in the data plus the function pointers, and cm_register registers them. 🫶

🔥 DESCRIPTION 🔥

This registers per-SoC low-level OMAP CM data and function pointers with the OMAP CM common interface. Simple concept, highkey important. 💖

The caller must keep the data pointed to by cld valid until it calls cm_unregister and it returns successfully. Do not let that data go stale before then, fr fr. 🚨

Returns:

• 0 upon success — slay. ✅
• -EINVAL if cld is NULL — no data, no registration, bestie. 🙈
• -EEXIST if cm_register has already been called without an intervening cm_unregister — one at a time, periodt. 💅

🦋 SEE ALSO 🦋

Kernel file ./arch/arm/mach-omap2/cm_common.c, plus these iconic little references: cm_split_idlest_reg(9), omap_cm_wait_module_ready(9), omap_cm_wait_module_idle(9), omap_cm_module_enable(9), omap_cm_module_disable(9), cm_unregister(9), omap2_cm_base_init(9), omap_cm_init(9). 👑

okay that's the whole page 💌 — source/version: ./arch/arm/mach-omap2, date: October 2026, page: cm_register(9).