omap_device_enable(9)
β¨ omap_device_enable(9) β from the Kernel API Manual β¨
okay so bestie, this is a kernel API manual page, and it's literally about waking up an omap_device and making it fully alive π
πΈ NAME πΈ
omap_device_enable β fully activate an omap_device π«Ά
π SYNOPSIS π
int omap_device_enable (struct platform_device *pdev );
π¦ ARGUMENTS π¦
pdevβ the platform device you want to activate β¨ like, the one you're bringing to life, no cap
π DESCRIPTION π
So the way this works is: this function does whatever is necessary for the hwmods underlying the omap_device od to be accessible and ready to operate π₯
What does "whatever is necessary" mean? Generally it involves:
- enabling clocks β°
- setting
SYSCONFIGregisters π - and in the future it may involve remuxing pins π (yes, future, as in not yet, don't come for me)
Heads up bestie: device drivers should call this function indirectly via pm_runtime_get*(). Like, that's the vibe β don't call it straight up, iykyk π
Return values, listen up:
- Returns
-EINVALif you call it when theomap_deviceis already enabled π (it's giving "girl, it's already on") - Otherwise it passes along the return value of
_omap_device_enable_hwmodsπ
π SEE ALSO π
Kernel file ./arch/arm/mach-omap2/omap_device.c β go read it, it's iconic π
_add_hwmod_clocks_clkdev(9)omap_device_build_from_dt(9)_omap_device_enable_hwmods(9)_omap_device_idle_hwmods(9)omap_device_alloc(9)omap_device_idle(9)omap_device_assert_hardreset(9)omap_device_deassert_hardreset(9)omap_device_late_idle(9)
π and that's the page! brought to you by the lovely humans over at ./arch/arm/mach-omap2, dated October 2026 β slay, periodt πβ¨
π¦ 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