omap_prcm_re...hain_handler(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– omap_prcm_register_chain_handler(9) πŸ’–

okay bestie, welcome to the Kernel API Manual β€” this is the page for omap_prcm_register_chain_handler, and yes the title got truncated with ... in the header, that's just how it is, we don't make the rules ✨


🌸 NAME 🌸

omap_prcm_register_chain_handler β€” sets up the PRCM chained interrupt handler using the parameters you hand it πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int omap_prcm_register_chain_handler (struct omap_prcm_irq_setup
*irq_setup );

like, that's the whole call. one struct pointer, one int coming back at you. iconic πŸ’…


✨ ARGUMENTS ✨

  • irq_setup β€” the hardware data describing the underlying PRM/PRCM. that's it, that's the vibe check. it's the hardware gossip the function needs 🫢

πŸ’œ DESCRIPTION πŸ’œ

okay so here's the tea: this function sets up the PRCM chained interrupt handler on the PRCM IRQ πŸ”₯

it also sets up one generic IRQ chip per PRM interrupt status/enable register pair β€” like, one chip per pair, no cap, that's just how it goes 🌈

and it returns stuff:

  • 0 when everything slays (success πŸ’–)
  • -EINVAL if you call it twice, or if you pass invalid arguments β€” so don't do that πŸ™ˆ
  • -ENOMEM on any other error 😭
lowkey important: calling it twice is a -EINVAL situation, so pls don't double-call. the kernel will not be amused πŸ’€

πŸŽ€ SEE ALSO πŸŽ€

like a whole friend group of related manpages, tbh β€” go read them, iykyk πŸ‘‘


and that's the page bestie!! πŸ’…βœ¨ source/version vibes live at ./arch/arm/mach-omap2, dated October 2026, and the page itself goes by omap_prcm_re...hain_handler(9) β€” yes, still truncated, we stan a mysterious queen πŸ§šβ€β™€οΈπŸ’œ mwah, bye!! πŸ“

πŸ“¦ where this page comes from