qcom_glink_receive_version(9)

💖 qcom_glink_receive_version(9) 💖

okay so bestie, this is a page straight out of the Kernel API Manual and it's literally about handling a negotiation message from the other side of a Glink link. it's short, it's sweet, and it slays at exactly one job. let's get into it 🎀

---

✨ NAME ✨

qcom_glink_receive_version — receive version/features from remote system

like, the whole vibe of this function is "the remote system said hi and told us what it can do" 🦋

---

🌸 SYNOPSIS 🌸

void qcom_glink_receive_version (struct qcom_glink *glink , u32 version
, u32 features );

no return value, no drama, just vibes and three arguments 💅

---

💜 ARGUMENTS 💜

• glink — pointer to transport interface
• version — remote version
• features — remote features

that's it. that's the whole squad. 🫶

---

⭐ DESCRIPTION ⭐

This function is called in response to a remote-initiated version/feature negotiation sequence.

okay so like, key detail: it's a response. the remote side kicks off the version/feature negotiation, and this function is what runs back at them. not me being the reply girl of the kernel 🔥

---

👑 SEE ALSO 👑

the whole Glink family reunion, fr fr:

• Kernel file ./drivers/rpmsg/qcom_glink_native.c
• struct glink_defer_cmd(9)
• struct glink_core_rx_intent(9)
• struct qcom_glink(9)
• struct glink_channel(9)
• qcom_glink_send_open_req(9)
• qcom_glink_receive_version_ack(9)
• qcom_glink_send_intent_req_ack(9)
• qcom_glink_advertise_intent(9)
• qcom_glink_handle_intent_req(9)
• qcom_glink_set_flow_control(9)

iykyk, these are all the sibling functions and structs you're gonna want to read next 💀✨

---

and that's the page!! 🧚 this little icon lives in ./drivers/rpmsg, and this edition is dated October 2026. take care of her, she's doing important negotiation work 💖🎀🦋