pruss_intc_unmap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pruss_intc_unmap(9) β€” Kernel API Manual πŸ’…

okay so welcome to the pruss_intc_unmap(9) page from the Kernel API Manual, bestie. Yes we are in the kernel API manual and yes we are gonna make it make sense. 🫢

πŸ’– NAME πŸ’–

pruss_intc_unmap β€” unconfigure the PRUSS INTC. That's the whole vibe: it takes the PRUSS INTC and unconfigures it, periodt. ✨

✨ SYNOPSIS ✨

void pruss_intc_unmap (struct pruss_intc *intc , unsigned long hwirq );

πŸŽ€ ARGUMENTS πŸŽ€

  • intc β€” PRUSS interrupt controller pointer. Like, the struct pruss_intc * itself β€” your main character controller pointer πŸ’…
  • hwirq β€” the system event number. It's an unsigned long, and it's giving β€œwhich system event are we talking about” energy. 🌸

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so this one is the undo button, but make it kernel: it undoes whatever was done in pruss_intc_map for a PRU core. No cap, that's the whole job. 😭

Mappings are reference counted, so resources are only disabled when there are no longer any users. Translation: it's not out here shutting things down while somebody else is still using them β€” the resources wait until the last user is gone. Iconic, honestly. πŸ‘‘

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/irqchip/irq-pruss-intc.c
  • struct pruss_intc_map_record(9)
  • struct pruss_intc_match_data(9)
  • struct pruss_intc(9)
  • struct pruss_host_irq_data(9)
  • pruss_intc_map(9)

mwah πŸ’– this lil page comes from the ./drivers/irqchip source tree, dated October 2026, and it's serving pruss_intc_unmap(9) energy all the way to the end β€” bye bestie! πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from