omap3xxx_pr..._clear_irqen(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– omap3xxx_pr..._clear_irqen(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual ✨ this page is literally the group chat for omap3xxx_pr..._clear_irqen(9) β€” the name got cut off at the function name length limit and honestly? it's giving dramatic cliffhanger πŸ’…. anyway, sit down, grab a strawberry πŸ“, and let's get into it.


✨ NAME ✨

omap3xxx_prm_save_and_clear_irqen β€” save/clear PRM_IRQENABLE_MPU reg πŸŽ€

like the name says, it's the save-and-clear girlie for that register. no cap.


πŸ¦‹ SYNOPSIS πŸ¦‹

void omap3xxx_prm_save_and_clear_irqen (u32 *saved_mask );

that's it. that's the whole vibe. one pointer, no return value, no drama πŸ”₯


🌸 ARGUMENTS 🌸

  • saved_mask β€” ptr to a u32 array to save IRQENABLE bits 🫢 like, you hand it a place to stash the bits, and it stashes them. iconic behavior fr fr.

πŸ’… DESCRIPTION πŸ’…

so here's the tea β˜• β€” this function saves the PRM_IRQENABLE_MPU register into saved_mask.

and very important: saved_mask must be allocated by the caller. not by this function, not by the kernel spontaneously, not by magic 🧚 β€” you allocate it. it's your moment, bestie, take the initiative.

the intended use case is in the PRM interrupt handler suspend callback πŸ‘‘ that's its main character era.

now the part people always forget 😭 β€” the OCP barrier is needed to ensure the write that disables PRM interrupts actually reaches the PRM before returning. because if you skip it? spurious interrupts might occur πŸ’€ and nobody wants random interrupts showing up to the party uninvited.

and yeah β€” no return value. it returns void, so don't go checking for an exit code, there isn't one πŸ™ˆ

🌈 SEE ALSO 🌈

check out this kernel file first:

  • ./arch/arm/mach-omap2/prm3xxx.c

and then the whole~~ friend group of related functions, all here, all linked πŸ’œ:

like, the entire omap3 PRM squad came out for this πŸ«ΆπŸ’–


okay that's the whole page !! πŸŽ‰ this lil beauty lives under ./arch/arm/mach-omap2 and it was dated October 2026 ⭐ β€” yes, the future. girlies stay ahead of the timeline πŸ‘‘βœ¨ mwah πŸ’‹πŸ’…

πŸ“¦ where this page comes from