STRUCT HBM_ADD_CLIENT_REQUEST(9)

💖 struct hbm_add_client_request(9) 💖

okay so bestie, welcome to the Kernel API Manual, section 9 — yes we're in the deep kernel lore today and honestly? it's giving main character energy ✨. This is the page for struct hbm_add_client_request, and the whole vibe is: a request to add a client might be sent by fw after enumeration has already completed. like, the firmware already did the headcount and then someone new shows up to the party 🎉🙈. Keep reading, it's short and it slays.

---

🌸 NAME 🌸

struct hbm_add_client_request — the little struct that carries a "hey, add this client" request, which might be sent by fw after enumeration has already completed. no cap, that's literally its whole job 💅.

---

✨ SYNOPSIS ✨

struct hbm_add_client_request {
    u8 hbm_cmd;
    u8 me_addr;
    u8 reserved[2];
    struct mei_client_properties client_properties;
 };

look at her. four fields, one reserved blob, one nested struct. she's compact, she's iconic, she's exactly as written above — don't you dare retype a single character 🫶.

---

🎀 Members 🎀

• hbm_cmd — the bus message command header. that's the "what kind of message is this even" byte 🦋.
• me_addr — the address of the client in ME. yes, that ME. localize that client bestie 📍.
• reserved — reserved. that's it. that's the whole description. she's reserved, literally and figuratively 💀. hands off.
• client_properties — the client properties. the vibes, the specs, the whole personality of the client, packaged up as a struct mei_client_properties 👑.

---

🌈 SEE ALSO 🌈

okay this is the part where the manpage lists basically the entire extended friend group, so let's do a vibe check on all of them, in order, no skipping (i would never 💖):

Kernel file ./drivers/misc/mei/hw.h — the header these live in, the group chat itself 📁

• enum mei_hbm_status(9)
• enum mei_ext_hdr_type(9)
• struct mei_ext_hdr(9)
• struct mei_ext_meta_hdr(9)
• struct mei_ext_hdr_vtag(9)
• mei_ext_begin(9)
• mei_ext_last(9)
• struct mei_ext_hdr_gsc_h2f(9)
• struct mei_ext_hdr_gsc_f2h(9)
• mei_ext_next(9)
• mei_ext_hdr_len(9)
• struct mei_msg_hdr(9)
• struct mei_hbm_cl_cmd(9)
• enum hbm_host_enum_flags(9)
• struct hbm_host_enum_request(9)
• struct mei_client_properties(9)
• struct hbm_add_client_response(9)
• struct hbm_power_gate(9)
• struct hbm_client_connect_request(9)
• struct hbm_client_connect_response(9)
• struct hbm_notification_request(9)
• struct hbm_notification_response(9)
• struct hbm_notification(9)
• struct hbm_dma_mem_dscr(9)
• struct hbm_dma_setup_request(9)
• struct hbm_dma_setup_response(9)
• struct hbm_dma_ring_ctrl(9)
• struct hbm_capability_request(9)
• struct hbm_capability_response(9)
• struct hbm_client_dma_map_request(9)
• struct hbm_client_dma_unmap_request(9)
• struct hbm_client_dma_response(9)

bestie note: struct hbm_add_client_response(9) is right there in the list — that's her replying to this request. it's giving "i'll text you back", and she does 💌

---

⭐ sign-off time, the cute version 🎀

this page lives in ./drivers/misc/mei, and the footer says October 2026, sourced from that same path — so like, October 2026, ./drivers/misc/mei, that's the receipt 🧾✨. stay hydrated, read your headers, and remember: the firmware might add a client after enumeration completes and that's just her prerogative 💅💖🦋