uart_port_trylock(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… uart_port_trylock(9) β€” the Kernel API Manual, bestie edition ✨

okay so picture this: it's a Kernel API Manual page, the vibes are immaculate, and it's all about uart_port_trylock. yes we're literally in the kernel, we're doing kernel things, and honestly? it's giving main character energy. let's get into it πŸŽ€


✨ NAME ✨

uart_port_trylock β€” try to lock the UART port πŸ¦‹

like, try. it's right there in the name. no promises, no drama, we just see if we can snag that lock. periodt πŸ’…


🌸 SYNOPSIS 🌸

bool uart_port_trylock (struct uart_port *up );

it hands you back a bool, it takes a struct uart_port *up, and that's the whole entire plot. no cap. 🫢


πŸ’– ARGUMENTS πŸ’–

  • up β€” pointer to UART port structure. that's it, that's the argument. give her the up and she'll do her thing 😭

πŸ¦‹ RETURN πŸ¦‹

  • True if the lock was acquired β€” slay, you got it, you're iconic πŸ‘‘
  • false otherwise β€” no lock for you this time, bestie, but like... it happens πŸ™ˆ
fr fr, that's the whole return contract. true = locked, false = not locked. don't overthink it, the manpage said what it said ✨

πŸ”₯ SEE ALSO πŸ”₯

okay this list is long, but every single one of these is part of the lore, so we're listing all of them, no skipping, no "etc." β€” iykyk 🌈

like, the whole friend group is here. go say hi to uart_port_unlock(9) especially β€” you two are gonna be besties πŸ«ΆπŸ’œ


⭐ lowkey important: this page lives in ./include/linux, and the version stamp is October 2026, and it's filed under uart_port_trylock(9). noted, archived, screenshotted for the group chat πŸ“ΈπŸ§š

and that's the page, bestie!! ./include/linux, October 2026, uart_port_trylock(9) β€” mwah, kiss the docs goodbye, you understood it the whole time πŸ’–πŸŽ€πŸ’…

πŸ“¦ where this page comes from