platform_get...ame_optional(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– platform_get_irq_byname_optional πŸ’–

okay bestie, welcome to the Kernel API Manual ✨ this one's a lil page from the kernel docs, platform_get_irq_byname_optional(9), and honestly? she's the chill, no-drama sibling of the IRQ getters. let's get into it πŸŽ€


🌸 NAME 🌸

platform_get_irq_byname_optional β€” get an optional IRQ for a device by name πŸ¦‹

like, she fetches an IRQ by name, but she's optional about it. lowkey the whole personality.


✨ SYNOPSIS ✨

int platform_get_irq_byname_optional (struct platform_device *dev ,
       const char *name );

that's the whole signature, no cap πŸ”₯


🫢 ARGUMENTS 🫢

  • dev β€” the platform device πŸ’» like, the device we're asking about
  • name β€” the IRQ name 🏷️ the string we're looking the IRQ up by

πŸ’… DESCRIPTION πŸ’…

so here's the tea β˜•: this one gets an optional IRQ by name, and honestly it works just like platform_get_irq_byname. same energy, same lookup.

but! the one difference β€” and this is the moment, this is her main character trait β€” she does not print an error message if an IRQ can not be obtained πŸ€«πŸ’€

fr fr, if the IRQ isn't there, she just... doesn't complain. no error spam in your dmesg. iconic behaviour, honestly. some of y'all need to learn this.

🌈 RETURN 🌈

  • non-zero IRQ number on success πŸŽ‰ (yay, we got one)
  • negative error number on failure 😭 (aw, didn't get one β€” but remember, no error message gets printed!)

πŸ‘‘ SEE ALSO πŸ‘‘

the whole squad, gathered for your convenience 🫢 and yes, they're all here, every single one:

that's the full roster, go read some more if you're obsessed πŸ§šπŸ’œ


aaaand that's the page bestie!! πŸŽ€ this lil gem lives in ./drivers/base and the version on deck is dated October 2026 β€” so yeah, fresh off the presses πŸ’– mwah, go forth and grab those optional IRQs πŸ’…βœ¨

πŸ“¦ where this page comes from