gsm_register_devices(9)

💖 gsm_register_devices(9) 💖

okay so bestie, welcome to the Kernel API Manual page for gsm_register_devices(9) — yes that's the whole header, the function name plus the manual section, and honestly? iconic of it.

---

✨ NAME ✨

gsm_register_devices — register all tty devices for a given mux index

like, all of them. the whole tty squad. for one mux index. that's the entire job, no cap.

---

🌸 SYNOPSIS 🌸

int gsm_register_devices (struct tty_driver *driver , unsigned int index
);

it returns an int, it takes two things, and the line break after index is just how the original wrapped it — don't come for me, I'm being faithful 💅

---

🎀 ARGUMENTS 🎀

• driver — the tty driver that describes the tty devices. it's the whole blueprint of the ttys, the main character of the argument list, the thing that gets to define what these devices even are 🫶
• index — the mux number. it's used to calculate the minor numbers of the ttys for this mux, and plot twist: it may differ from the position in the mux array. so like, don't assume index == array slot, because it fr fr might not be 😭

---

🦋 SEE ALSO 🦋

so there's a kernel file for this one, and it lives at ./drivers/tty/n_gsm.c — go read it if you want the real tea. and then the whole extended gsm family, because this is a very social function and everyone it knows has a manpage:

• 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_unregister_devices(9) — hi yes the counterpart, the breakup function 💔
• 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_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)

that's the whole group chat. every single one of them is a (9) section page, and yes i typed all of them out, because the vibe check is: keep every detail 💀

---

and that's the page!! tiny function, huge friend group. this lil manual lives under ./drivers/tty and it's dated October 2026 — so like, future-dated slay 👑. mwah, go register those ttys bestie, gsm_register_devices(9) out 🦋✨🎀