irq_domain_xlate_twocell(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay bestie, say hi to irq_domain_xlate_twocell(9) β€” she’s from the Kernel API Manual, and she is literally the Generic xlate for direct two cell bindings ✨. This is the function handling that two-cell device tree interrupt translation, and she keeps it direct, no cap πŸ’….


✨ SYNOPSIS ✨

       int irq_domain_xlate_twocell (struct irq_domain *d , struct device_node
       *ctrlr , const u32 *intspec , unsigned int intsize , irq_hw_number_t
       *out_hwirq , unsigned int *out_type );

πŸŽ€ ARGUMENTS πŸŽ€

These are the besties she takes, and every single one matters 🫢:

  • d β€” the interrupt domain involved in the translation. main character domain energy fr fr πŸ‘‘
  • ctrlr β€” the device tree node for the device whose interrupt is translated.
  • intspec β€” the interrupt specifier data from the device tree.
  • intsize β€” the number of entries in intspec.
  • out_hwirq β€” pointer to storage for the hardware interrupt number.
  • out_type β€” pointer to storage for the interrupt type.

πŸ¦‹ DESCRIPTION πŸ¦‹

This is the Device Tree IRQ specifier translation function, and she works with two cell bindings where the cell values map directly to the hwirq number and linux irq flags. The way that’s so direct? Obsessed, honestly πŸ’œ. No detours, no extra drama β€” the values map straight through, periodt.


πŸ’œ SEE ALSO πŸ’œ

Kernel file ./kernel/irq/irqdomain.c is where she lives, and here’s the whole linked-up squad β€” every single one, no skips, bestie 🌈:


irq_domain_xlate_twocell(9) is serving from ./kernel/irq, dated October 2026 β€” that’s the cute little source/version footer, bestie. Now go translate those two cells and slay πŸ’–βœ¨

πŸ“¦ where this page comes from