alchemy_gpio2_disable_int(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… alchemy_gpio2_disable_int β€” kernel API manual, bestie edition πŸŽ€

okay so real talk, this one's a tiny little icon in the Alchemy GPIO cinematic universe β€” it's all about turning off one GPIO2 pin's contribution to a shared irq. yes, shared. yes, irq. we're in the kernel now, drink some water πŸ’–


✨ NAME ✨

alchemy_gpio2_disable_int β€” Disable a GPIO2 pins' shared irq contribution.

like, that's the whole vibe. one pin, one shared irq, contribution: removed. periodt πŸ’…


🌸 SYNOPSIS 🌸

void alchemy_gpio2_disable_int (int gpio2 );

that's it. that's the whole call. a void return (so nothing comes back, don't @ me looking for a result), and one int going in 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • gpio2 β€” The GPIO2 pin to activate (200...215).

ok so bestie, quick vibe check: the doc literally says "to activate" even though the function is disable β€” that's what the page says, I'm just the messenger πŸ™ˆ what you actually need to know is the range: it's a GPIO2 pin, numbered 200...215. keep it in that lane, iykyk ⭐


πŸ”₯ DESCRIPTION πŸ”₯

so the actual description here is iconic in its minimalism: it just points you at alchemy_gpio2_enable_int for more information. that's it. go read the enable one, it's the main character of this particular saga πŸ‘‘

ngl it's giving "figure it out bestie, the sibling function explains everything" energy, and honestly? valid. πŸ’€


πŸ’œ SEE ALSO πŸ’œ

the whole friend group fr fr β€” go say hi to all of them 🌈


heads up babe: the original page gives you zero extra detail in DESCRIPTION. everything real lives in alchemy_gpio2_enable_int. don't come for me, come for the docs πŸ’…

and that's the page!! brought to you by the kernel API manual, source ./arch/mips/include/asm/mach-a..., dated October 2026 β€” mwah, slay, go disable some interrupts responsibly πŸ’–βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from