__tty_alloc_driver(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

__tty_alloc_driver β€” allocate a tty driver. Yes bestie, this is the Kernel API Manual page for __tty_alloc_driver(9), and we are gonna get through it together ✨


🌸 SYNOPSIS 🌸

struct tty_driver * __tty_alloc_driver (unsigned int lines , struct
module *owner , unsigned long flags );

πŸŽ€ ARGUMENTS πŸŽ€

  • lines β€” count of lines this driver can handle at most, like its absolute max capacity bestie πŸ’…
  • owner β€” module which is responsible for this driver, the accountable icon πŸ‘‘
  • flags β€” some of enum tty_driver_flag; they will be set in driver->flags ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so major heads-up, bestie: this should not be called directly. tty_alloc_driver should be used instead. That is the whole vibe. __tty_alloc_driver is not the one you call yourself, tty_alloc_driver is 🫢


✨ RETURN ✨

It gives you a struct tty_driver or a PTR-encoded error, so use IS_ERR and friends to check what you actually got. No cap 😭


🌈 SEE ALSO 🌈

Kernel file: ./drivers/tty/tty_io.c. And the related-pages group chat is literally right here, no skipping:

With all the love from the ./drivers/tty source tree, Kernel API Manual, dated October 2026, signed __tty_alloc_driver(9) πŸ’–πŸ«Άβœ¨

πŸ“¦ where this page comes from