platform_get_irq_affinity(9)

📦 version 7.3.1, in nixpkgs unstable

👑 platform_get_irq_affinity — the kernel API manual, bestie edition ✨

okay so this page is platform_get_irq_affinity(9) from the Kernel API Manual, and it's genuinely one of those little functions that eats and leaves no crumbs if you use it right 🫶

🌸 NAME 🌸

platform_get_irq_affinity — literally just grab an optional IRQ for a device, plus its affinity 💅

✨ SYNOPSIS ✨

int platform_get_irq_affinity (struct platform_device *dev , unsigned
int num , const struct cpumask **affinity );

like, that's the whole signature, no cap. write it exactly like that 📝

🎀 ARGUMENTS 🎀

  • dev — the platform device, your main character here 👑
  • num — the interrupt number index 🔢
  • affinity — an optional cpumask pointer that gets you the affinity of a per-cpu interrupt 🧚

💖 DESCRIPTION 💖

So the vibe is: this gets an interrupt for a platform device. simple, iconic, does what it says 🦋

bestie listen to me — device drivers should check the return value for errors so as to not pass a negative integer value to the request_irq APIs 😭 that's not a suggestion, that's the whole plot

Optional affinity info gets handed to you in the affinity pointer if available, and NULL otherwise. that's it, that's the deal ⭐

🔥 RETURN 🔥

  • non-zero interrupt number on success — we love a win 💜
  • negative error number on failure — check for this, fr fr 💀

🌈 SEE ALSO 🌈

the whole friend group, no one gets left out 💕 kernel file ./drivers/base/platform.c plus:

and that's the page!! mwah 💋 this one lives in ./drivers/base, dated October 2026, and it's platform_get_irq_affinity(9) — go forth and check your return values, queen 🎀✨

📦 where this page comes from