gsm_control_wait(9)
π gsm_control_wait(9) β like, the Kernel API Manual, but make it make sense
okay so bestie, welcome to gsm_control_wait(9) β¨ this is a page from the Kernel API Manual and it's honestly short and sweet β we're waiting on a control message to finish, that's the whole vibe. let me walk you through it π«Ά
πΈ NAME πΈ
gsm_control_wait β wait for a control to finish π
like literally just. sit there. until the control is done. periodt.
β¨ SYNOPSIS β¨
int gsm_control_wait (struct gsm_mux *gsm , struct gsm_control *control
);
two args, one int back. no cap, that's it π₯
π ARGUMENTS π
gsmβ the GSM mux π¦ (yes that's the whole description, she's lowkey mysterious)controlβ the control we are waiting on β³ like, the specific one. the main character of this function ngl.
π DESCRIPTION π
so here's the tea β: gsm_control_wait waits for the control to complete or time out. that's the whole job, and she does it well π
when it's done, it frees any used resources β cleanup queen, we stan π§Ήβ¨ β and then it returns 0 for success π
but if it doesn't go well? if the remote rejected it, or straight up ignored the request? π then you get an error back instead. rude of the remote honestly, but that's the contract.
so real talk: check that return value. 0 = slay, error = the remote was not giving π
π SEE ALSO π
okay this section is a whole friend group, so buckle up bestie β all of these live in the kernel file ./drivers/tty/n_gsm.c π and they're all here, every single one, i'm not skipping anybody π
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_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_free(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)
see? everybody showed up to the party π iykyk π
and that's the whole page, bestie β short, iconic, no filler π
signed off from ./drivers/tty in October 2026 β gsm_control_wait(9) forever πβ¨π
π¦ 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