tty_port_carrier_raised(9)
π tty_port_carrier_raised(9) π
okay so first things first, bestie: this page lives in the Kernel API Manual, and the function we're stanning is literally called tty_port_carrier_raised. yes it's a mouthful. no we don't make the rules. π
β¨ NAME β¨
tty_port_carrier_raised β the carrier raised check, aka "is the line actually up, or are we just pretending" π
πΈ SYNOPSIS πΈ
bool tty_port_carrier_raised (struct tty_port *port );
that's it. that's the whole summoning ritual. she's a bool, she takes one pointer, she does one job. main character energy fr fr β¨
π¦ ARGUMENTS π¦
portβ the tty port in question π«Ά like, the actualstruct tty_port *you're asking about. that's the whole argument list. one (1) port. iconic, honestly.
π DESCRIPTION π
so this is a wrapper for the carrier detect logic π that's the whole vibe. you call her, she handles the carrier-detect situation for you.
and why does she exist? for the moment, this is used to hide some internal details π β like, the messy stuff is tucked behind this nice little function so you don't have to look at it. very "don't worry about it bestie, I got you" of her.
heads up though π β the docs literally say this will eventually become entirely internal to the tty port. so like, she's on her way to becoming a private girly. don't get too attached to calling her from the outside, iykyk π
π₯ SEE ALSO π₯
no because the SEE ALSO section on this one ATE. it's giving family reunion. the whole tty_port extended universe is here π and hey, the Kernel file is ./drivers/tty/tty_port.c β that's where she lives, go say hi π
tty_port_init(9)tty_port_link_wq(9)tty_port_link_device(9)tty_port_register_device(9)tty_port_register_device_attr(9)tty_port_register_device_attr_serdev(9)tty_port_unregister_device(9)tty_port_destroy(9)tty_port_put(9)tty_port_tty_get(9)tty_port_tty_set(9)tty_port_shutdown(9)tty_port_hangup(9)tty_port_tty_hangup(9)tty_port_tty_vhangup(9)tty_port_tty_wakeup(9)tty_port_raise_dtr_rts(9)tty_port_lower_dtr_rts(9)tty_port_block_til_ready(9)tty_port_close_start(9)tty_port_close_end(9)tty_port_close(9)tty_port_install(9)tty_port_open(9)
like I said. the whole squad. go read them too, they're all slaying in their own lanes π
and that's the page, babe π«Ά sourced from ./drivers/tty, dated October 2026, served up fresh from the Kernel API Manual β mwah, go check that carrier, ily, bye ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms