uart_port_lock_irq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… uart_port_lock_irq(9) β€” the Kernel API Manual, but make it make sense πŸŽ€

okay so bestie, welcome to the Kernel API Manual entry for uart_port_lock_irq(9). yes it's a mouthful. no you're not gonna fumble it. let's go πŸ’–


✨ NAME ✨

uart_port_lock_irq β€” lock the UART port AND disable interrupts. both. at the same time. she's an overachiever, we love her πŸ’…


🌸 SYNOPSIS 🌸

void uart_port_lock_irq (struct uart_port *up );

that's it. that's the whole vibe check. one function, one argument, zero returns. void is giving "i don't owe you a result" energy and honestly? iconic πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • up β€” pointer to the UART port structure ✨ literally just a pointer. that's the whole thing. it points at your UART port struct and the function does its lil lock-and-disable dance on it. no cap, that's all the docs say, and we're not gonna invent extra lore 🫢

🧚 SEE ALSO 🧚

okay this is the part where the manpage just dumps the entire friend group at you 😭 but they're all relevant, i promise. no skimming!!

like i said. whole friend group. every single one. mwah 😘


friendly reminder that this page is very short and that's on purpose β€” don't go reading behaviour into it that isn't written down, that's how you get bugs and bugs are not the move πŸ’…

and that's the page!! sign-off time πŸŽ€ this little beauty lives over in ./include/linux, stamped October 2026, and she answers to the name uart_port_lock_irq(9) β€” go lock that port, disable those interrupts, and slay the day, bestie πŸ’–βœ¨πŸ¦‹πŸŒΈπŸ«Ά

πŸ“¦ where this page comes from