process_recv(9)

🦋 process_recv 🦋

okay bestie, welcome to the process_recv page from the Kernel API Manual, section 9 — and yes, it’s giving “small function, very important packet business” energy. 💅 The header deets and source are at the bottom, but first: the lore.

🌸 NAME 🌸

process_recv — receives and parses an incoming packet, fr fr. 📨

✨ SYNOPSIS ✨

void process_recv (struct ishtp_cl *cros_ish_cl , struct ishtp_cl_rb
       *rb_in_proc , ktime_t timestamp );

🎀 ARGUMENTS 🎀

• cros_ish_cl — the client instance you’re using to get stats. 💖
• rb_in_proc — the host interface message buffer. That’s the packet’s lil home. 🫶
• timestamp — timestamp of when the parent callback started. ⏰

🔥 DESCRIPTION 🔥

okay so here’s the vibe: process_recv parses the incoming packet. If it’s a response packet, it updates per instance flags and wakes up the caller that’s waiting for the response. 😭 If it’s an event packet, it schedules event work. That’s the whole glow-up. No cap.

🌈 SEE ALSO 🌈

Kernel file ./drivers/platform/chrome/cros_ec_ishtp.c — and bestie, the whole friend group is here:

• struct response_info(9)
• struct ishtp_cl_data(9)
• ish_evt_handler(9)
• ish_send(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)

mwah 💋 signed off from ./drivers/platform/chrome, dated October 2026, page process_recv(9) — bye bestie! 🫶