omap_device_enable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ 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 SYSCONFIG registers πŸ“
  • 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 -EINVAL if you call it when the omap_device is 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 πŸ“–


πŸ’œ 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