mei_hbm_prop_req(9)

💖 NAME 💖

mei_hbm_prop_req — bestie, this one's literally "request property for a single client" ✨

✨ SYNOPSIS ✨

int mei_hbm_prop_req (struct mei_device *dev , unsigned long start_idx
);

🎀 ARGUMENTS 🎀

• dev — the device structure, aka the main character of this whole story 👑
• start_idx — the client index where the search kicks off, like picking which seat to start looking from 🪑

🦋 RETURN 🦋

0 on success and < 0 on failure. That's it, that's the whole vibe check — zero means slay, negative means something went off 😭

🌸 SEE ALSO 🌸

Kernel file ./drivers/misc/mei/hbm.c — and omg the whole squad shows up here, no cap:

• 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_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_fw_disconnect_req(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)

okay that's a wrap, bestie 🫶 this page lives over in ./drivers/misc/mei, dated October 2026, and it goes by mei_hbm_prop_req(9) — go read the rest of the kernel docs, ily, bye 💜