omap44xx_prm...pending_irqs(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… omap44xx_prm_read_pending_irqs(9) β€” like, the full glow-up

okay bestie, so this is a page straight outta the Kernel API Manual β€” yes, the whole omap44xx_prm...pending_irqs(9) situation β€” and it's honestly such a little icon. it doesn't return anything, it just quietly does its job, which is very demure, very mindful of it. let's get into it 🫢


✨ NAME ✨

omap44xx_prm_read_pending_irqs β€” reads the pending PRM MPU IRQs and drops them into @events. that's the whole vibe, no cap πŸ’–


🌸 SYNOPSIS 🌸

void omap44xx_prm_read_pending_irqs (unsigned long *events );

no return value, she just does. main character energy honestly πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • events β€” a pointer to two consecutive u32s, and bestie, you have to preallocate them yourself. the function is not gonna do your homework for you πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea: it reads the PRM_IRQSTATUS_MPU* bits, ANDs them together with the currently-enabled PRM MPU IRQs (bitwise AND, the whole & moment ✨), and then stores the result into those two u32s that events is pointing at.

that's it. that's the function. no return value β€” she's a void, she gives nothing back and honestly? iconic πŸ’…

lowkey the way this is basically "what's pending, but only the stuff that's actually turned on" β€” vibe check passed, fr fr 🌈


πŸ‘‘ SEE ALSO πŸ‘‘

like, go read these next, they're all in the kernel file ./arch/arm/mach-omap2/prm44xx.c and they're all giving cousin energy 🧚


and that's the whole page, bestie πŸ“ shoutout to the source tree ./arch/arm/mach-omap2, dated October 2026, still serving looks in the Kernel API Manual πŸ’œ tysm for reading, mwah πŸ’‹

πŸ“¦ where this page comes from