STRUCT ISHTP_CL_DATA(9)

✨ struct ishtp_cl_data(9) ✨

okay so bestie, this is the <pink>Kernel API Manual</pink> moment for struct ishtp_cl_data, and it's literally giving "per ISH TP Client" realness 💅. it's the little data home for one client, and we're gonna walk through it together, no cap 🫶.

---

🌸 NAME 🌸

struct ishtp_cl_data — encapsulate per ISH TP Client 💖

---

✨ SYNOPSIS ✨

struct ishtp_cl_data {
    struct ishtp_cl *cros_ish_cl;
    struct ishtp_cl_device *cl_device;
    struct response_info response;
    struct work_struct work_ishtp_reset;
    struct work_struct work_ec_evt;
    struct cros_ec_device *ec_dev;
 };

---

👑 Members 👑

• cros_ish_cl — the ISHTP firmware client instance, like the main character of the firmware situation 🦋
• cl_device — the ISHTP client device instance, its ride-or-die companion 💫
• response — response info that gets passed between ish_send and process_recv, the gossip relay between those two 🔥
• work_ishtp_reset — the work queue reset handling, aka the "we need to reset, let's queue it up" energy ⭐
• work_ec_evt — werk werk werk, it's the work queue for EC events 🎀
• ec_dev — the CrOS EC MFD device, iconic multi-function device vibes 👑

---

💜 Description 💜

this structure is used to store per client data. periodt. it's literally the lil' storage cubby for each client, and that's the whole vibe 💖.

---

🌈 SEE ALSO 🌈

besties you should also meet, all from the kernel file ./drivers/platform/chrome/cros_ec_ishtp.c:

• struct response_info(9)
• ish_evt_handler(9)
• ish_send(9)
• process_recv(9)
• ish_event_cb(9)
• cros_ish_init(9)
• cros_ish_deinit(9)
• prepare_cros_ec_rx(9)
• cros_ec_ishtp_probe(9)
• cros_ec_ishtp_remove(9)
• cros_ec_ishtp_reset(9)
• cros_ec_ishtp_suspend(9)
• cros_ec_ishtp_resume(9)

---

and that's the whole struct, bestie! now go forth and slay your ISH TP client knowledge 💅✨

---

shoutout to ./drivers/platform/chrome for holding it down, and to the October 2026 date for being so forward-thinking, we love a futuristic footer 🎀💖