loader_cl_send(9)

💖 loader_cl_send(9) 💖

🌸 NAME 🌸

loader_cl_send — Send message from host to firmware.

okay so this one is straight out of the Kernel API Manual, and it's giving "host wants to slide a message into firmware" energy. Very main character. Very ishtp. We love a little host-to-firmware communication moment 💅✨

---

🛰️ SYNOPSIS 🛰️

int loader_cl_send (struct ishtp_cl_data *client_data , u8 *out_msg ,
       size_t out_size , u8 *in_msg , size_t in_size );

---

🧾 ARGUMENTS 🧾

Bestie, here's the cast of characters — no skips, no cuts, we're covering everybody:

• client_data — Client data instance. Your little context buddy 🫶
• out_msg — Message buffer to be sent to firmware. This is the outgoing mail, fr fr 📬
• out_size — Size of out going message. Yes, "out going" with a space — that's literally what the page says, and I respect the icon behavior 💅
• in_msg — Message buffer where the incoming data copied. This buffer is allocated by calling — and yes, the sentence just stops there in the original 😭 iconic, honestly.
• in_size — Max size of incoming message. The ceiling, the limit, the vibe check for incoming data ✨

---

🔁 RETURN 🔁

Number of bytes copied in the in_msg on success, negative error code on failure.

So: happy path = bytes copied 💖, sad path = negative error code 😭. Keep that in mind, bestie.

---

👀 SEE ALSO 👀

Kernel file ./drivers/hid/intel-ish-hid/ishtp-fw-loader.c — plus the whole squad:

• enum ish_loader_commands(9)
• struct loader_msg_hdr(9)
• struct response_info(9)
• get_firmware_variant(9)
• process_recv(9)
• loader_cl_event_cb(9)
• ish_query_loader_prop(9)
• ish_fw_xfer_ishtp(9)
• ish_fw_xfer_direct_dma(9)
• ish_fw_start(9)
• load_fw_from_host(9)
• loader_init(9)
• loader_ishtp_cl_probe(9)
• loader_ishtp_cl_remove(9)
• loader_ishtp_cl_reset(9)

---

xoxo, your kernel bestie 💜 — shipped from ./drivers/hid/intel-ish-hid, dated October 2026, periodt. 🎀