gsm_process_negotiation(9)

💅 gsm_process_negotiation — like, the Kernel API Manual page, bestie

okay so picture this: you're deep in Kernel API Manual territory, right in the guts of the kernel's GSM muxing situation, and there's this one little function whose whole job is "hey, the reply came back, let's deal with it." That's her. That's the main character. 🎀

---

✨ NAME ✨

gsm_process_negotiation — the function that processes the parameters we just received (yes, that's literally the whole vibe) 💖

---

🌸 SYNOPSIS 🌸

int gsm_process_negotiation (struct gsm_mux *gsm , unsigned int addr ,
       unsigned int cr , const struct gsm_dlci_param_bits *params );

look at her go. four arguments, one int coming back at you, no cap. 🔥

---

🦋 ARGUMENTS 🦋

• gsm — the GSM channel, the whole entire context, the stage she performs on 💅
• addr — the DLCI address, aka which channel we're talking about 🎀
• cr — command/response, the little indicator of which one this message is ✨
• params — the encoded parameters, fresh out of the parameter negotiation message, still warm 🍓

---

👑 DESCRIPTION 👑

okay so here's the tea: this one gets called when the response to our parameter negotiation command shows up. You sent the command, you waited, and now the reply is here — and this function is the one that handles that moment. It's giving "the text came back, time to read it." 💀✨

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/tty/n_gsm.c, and honestly the whole friend group is here — this function rolls deep:

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_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)

not a single one skipped, bestie. the whole roster. 🫶

---

ok and before you go — this page lives in ./drivers/tty, it's dated October 2026, and it came to you thanks to the source/version crew over at the Kernel file ./drivers/tty/n_gsm.c. periodt. 💜✨