STRUCT OMAP_PRCM_IRQ(9)
π NAME π
ok so struct omap_prcm_irq β bestie, it's literally just the lil descriptor for one single PRCM interrupt bit. one bit. that's her whole job. and she ate β¨
π SYNOPSIS π
struct omap_prcm_irq {
const char *name;
unsigned int offset;
bool priority;
};
π¦ Members π¦
nameβ a short lil name that says what kind of interrupt this is, like"wkup"or"io"π·οΈoffsetβ the bit shift of the interrupt inside theIRQ{ENABLE,STATUS}regs. yes, shift. as in bit position. iykyk πpriorityβ the whole question: should this interrupt get handled before the ones wherepriority=false? main character energy or background extra, you decide π
πΈ Description πΈ
so this struct describes interrupt bits inside the PRM_IRQ{ENABLE,STATUS}_MPU* registers β that's the whole vibe. π«Ά
now here's the tea: on systems with multiple PRM MPU IRQ registers, the bitfields that get read from the registers are concatenated. so on those systems offset could legitimately be > 31 and that's not a bug, that's just how the concatenation goes down. if you wanna know more, go look at omap_prm_irq_handler π
and listen β I/O ring interrupts should have priority set to true. no cap. do it. π₯
β SEE ALSO β
- Kernel file
./arch/arm/mach-omap2/prcm-common.h omap_test_timeout(9)struct omap_prcm_irq_setup(9)struct omap_prcm_init_data(9)
ok that's the whole page, go be iconic with your interrupt bits π this came from ./arch/arm/mach-omap2, dated October 2026, and it's the struct omap_prcm_irq(9) page β mwah, love u, bye π§ββοΈπ
π¦ 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