gsm_dlci_free(9)
π gsm_dlci_free
okay so real talk β this little page comes straight out of the Kernel API Manual, section 9, and it's one of those tiny-but-iconic functions that does exactly what it says on the label. no lore, no plot twists, just a DLCI getting freed. let's get into it π
β¨ NAME β¨
gsm_dlci_free β free DLCI π¦
like. that's the whole thing. it frees the DLCI. main character energy, zero notes.
πΈ SYNOPSIS πΈ
void gsm_dlci_free (struct tty_port *port );
returns nothing (void, she gives nothing and takes nothing π
) and takes exactly one thing: the port.
π ARGUMENTS π
portβ the tty port for the DLCI you wanna free. that's it, that's the whole parameter π«Ά
π DESCRIPTION π
Free up a DLCI. periodt. no cap, that's the entire job description π₯
okay but the one detail you cannot skip: it can sleep. literally, it is allowed to sleep π΄ β so be a thoughtful bestie and keep that in mind wherever you're calling it from.
don't sleep on the "can sleep" note (pun fully intended) β it's the only caveat on this whole page and it's there for a reason π
π SEE ALSO π
bestie the squad here is huge, so buckle up. all of these live in the kernel file ./drivers/tty/n_gsm.c πβ¨
gsm_fcs_add(9)gsm_fcs_add_block(9)gsm_read_ea(9)gsm_read_ea_val(9)gsm_encode_modem(9)gsm_encode_params(9)gsm_register_devices(9)gsm_unregister_devices(9)gsm_print_packet(9)gsm_stuff_frame(9)gsm_send(9)gsm_dlci_clear_queues(9)gsm_response(9)gsm_command(9)gsm_data_alloc(9)gsm_send_packet(9)gsm_is_flow_ctrl_msg(9)gsm_data_kick(9)__gsm_data_queue(9)gsm_data_queue(9)gsm_dlci_data_output(9)gsm_dlci_data_output_framed(9)gsm_dlci_modem_output(9)gsm_dlci_data_sweep(9)gsm_dlci_data_kick(9)gsm_control_command(9)gsm_control_reply(9)gsm_process_modem(9)gsm_process_negotiation(9)gsm_control_modem(9)gsm_control_negotiation(9)gsm_control_rls(9)gsm_control_message(9)gsm_control_response(9)gsm_control_keep_alive(9)gsm_control_transmit(9)gsm_control_retransmit(9)gsm_control_send(9)gsm_control_wait(9)gsm_dlci_close(9)gsm_dlci_open(9)gsm_dlci_negotiate(9)gsm_dlci_t1(9)gsm_dlci_begin_open(9)gsm_dlci_set_opening(9)gsm_dlci_set_wait_config(9)gsm_dlci_begin_close(9)gsm_dlci_data(9)gsm_dlci_command(9)gsm_kick_timer(9)gsm_dlci_copy_config_values(9)gsm_dlci_config(9)gsm_dlci_alloc(9)gsm_dlci_release(9)gsm_queue(9)gsm0_receive_state_check_and_fix(9)gsm0_receive(9)gsm1_receive_state_check_and_fix(9)gsm1_receive(9)gsm_error(9)gsm_cleanup_mux(9)gsm_activate_mux(9)gsm_free_mux(9)gsm_free_muxr(9)gsm_alloc_mux(9)gsmld_output(9)gsmld_write_trigger(9)gsmld_write_task(9)gsmld_attach_gsm(9)gsmld_detach_gsm(9)gsmld_flush_buffer(9)gsmld_close(9)gsmld_open(9)gsmld_write_wakeup(9)gsmld_read(9)gsmld_write(9)gsmld_poll(9)gsm_modem_upd_via_data(9)gsm_modem_upd_via_msc(9)gsm_modem_update(9)gsm_wait_modem_change(9)
go off, n_gsm.c, you absolute icon πβ
that's the whole page, bestie β short, sweet, and to the point. this one was served fresh from ./drivers/tty in the October 2026 Kernel API Manual, section 9. mwah, go free some DLCIs ππ
π¦ 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