mei_hbm_fw_disconnect_req(9)

🌸 NAME 🌸

okay bestie, this is mei_hbm_fw_disconnect_req(9) from the Kernel API Manual, and it's literally the disconnect request that the ME firmware starts — the host then sends the disconnect response. Cleanup-era main character energy, no cap 🧚💖

✨ SYNOPSIS ✨

int mei_hbm_fw_disconnect_req (struct mei_device *dev , struct
       hbm_client_connect_request *disconnect_req );

🎀 ARGUMENTS 🎀

• dev — the device structure. The device-structure bestie in question 💅
• disconnect_req — disconnect request bus message from the me. Yep, that's the bus message, periodt 🦋

💜 RETURN 💜

• -ENOMEM on allocation failure. That's the return tea, and it's giving "allocation said nope" 😭

🌈 SEE ALSO 🌈

• Kernel file: ./drivers/misc/mei/hbm.c
• mei_cl_conn_status_to_errno(9)
• mei_hbm_write_message(9)
• mei_hbm_idle(9)
• mei_hbm_reset(9)
• mei_hbm_hdr(9)
• mei_hbm_cl_hdr(9)
• mei_hbm_cl_write(9)
• mei_hbm_cl_addr_equal(9)
• mei_hbm_cl_find_by_cmd(9)
• mei_hbm_start_wait(9)
• mei_hbm_start_req(9)
• mei_hbm_dma_setup_req(9)
• mei_hbm_capabilities_req(9)
• mei_hbm_enum_clients_req(9)
• mei_hbm_me_cl_add(9)
• mei_hbm_add_cl_resp(9)
• mei_hbm_fw_add_cl_req(9)
• mei_hbm_cl_notify_req(9)
• notify_res_to_fop(9)
• mei_hbm_cl_notify_start_res(9)
• mei_hbm_cl_notify_stop_res(9)
• mei_hbm_cl_notify(9)
• mei_hbm_cl_dma_map_req(9)
• mei_hbm_cl_dma_unmap_req(9)
• mei_hbm_prop_req(9)
• mei_hbm_pg(9)
• mei_hbm_stop_req(9)
• mei_hbm_cl_flow_control_req(9)
• mei_hbm_add_single_tx_flow_ctrl_creds(9)
• mei_hbm_cl_tx_flow_ctrl_creds_res(9)
• mei_hbm_cl_disconnect_req(9)
• mei_hbm_cl_disconnect_rsp(9)
• mei_hbm_cl_disconnect_res(9)
• mei_hbm_cl_connect_req(9)
• mei_hbm_cl_connect_res(9)
• mei_hbm_cl_res(9)
• mei_hbm_pg_enter_res(9)
• mei_hbm_pg_resume(9)
• mei_hbm_pg_exit_res(9)
• mei_hbm_config_features(9)
• mei_hbm_version_is_supported(9)
• mei_hbm_dispatch(9)

cute lil sign-off bestie: this page lives under ./drivers/misc/mei, the version/date stamp is October 2026, and the page is mei_hbm_fw_disconnect_req(9) 🫶💖✨