xilinx_cpm_pcie_intx_map(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xilinx_cpm_pcie_intx_map β€” bestie's guide to hooking up INTx

ok so this is a page from the Kernel API Manual (yes, the kernel has its own manual, she's fancy) and it's all about xilinx_cpm_pcie_intx_map, which is honestly the most niche little function ever and I'm obsessed πŸ’–


✨ NAME ✨

xilinx_cpm_pcie_intx_map β€” Set the handler for the INTx and mark IRQ as valid πŸŽ€

Like, that's literally her whole job. She sets the handler for the INTx and marks the IRQ as valid. Queen behavior, no notes. πŸ‘‘


🌸 SYNOPSIS 🌸

int xilinx_cpm_pcie_intx_map (struct irq_domain *domain , unsigned int irq , irq_hw_number_t hwirq );

It returns an int, bestie. Keep that in your pocket, we'll come back to it. 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

Three little besties walk into the function:

  • domain β€” the IRQ domain. That's her home base, her whole vibe check. 🌈
  • irq β€” the Virtual IRQ number. The soft, abstract, "what the OS thinks it is" version. ✨
  • hwirq β€” the HW interrupt number. The real, physical, hardwired one. irq_hw_number_t, no less. πŸ’…

πŸ’œ RETURN πŸ’œ

Always returns 0. Not "sometimes", not "on success" β€” always. She literally cannot fail. main character energy fr fr. 🌟


πŸ”₯ SEE ALSO πŸ”₯

ok here's the little friend group, all of them live in the kernel file ./drivers/pci/controller/pcie-xilinx-cpm.c:

go read their pages too, iykyk 🧚


ngl this one's short but she still ate. tiny function, zero drama, always returns 0. periodt. πŸ’€

and that's the whole page, bestie πŸ“ this came out of ./drivers/pci/controller, dated October 2026, and it's living over in the Kernel API Manual section β€” mwah, go forth and map those interrupts πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from