STRUCT QCOM_GLINK(9)

✨ struct qcom_glink(9) ✨

okay bestie, this is struct qcom_glink — and no, it's not a social media thing 💅 it's the driver context that relates to one remote subsystem. one. single. subsystem. it's giving main character energy for exactly one remote. 🫶

this page lives in section 9 of the Kernel API Manual, so you know it's the fancy kernel-internals section, iykyk.

🌸 SYNOPSIS 🌸

struct qcom_glink {
    struct device *dev;
    const char *label;
    struct qcom_glink_pipe *rx_pipe;
    struct qcom_glink_pipe *tx_pipe;
    struct work_struct rx_work;
    spinlock_t rx_lock;
    struct list_head rx_queue;
    spinlock_t tx_lock;
    spinlock_t idr_lock;
    struct idr lcids;
    struct idr rcids;
    unsigned long features;
    bool intentless;
    wait_queue_head_t tx_avail_notify;
    bool sent_read_notify;
    bool abort_tx;
 };

like, look at her. so many fields. so much going on. literally iconic. 🎀 copy it exactly bestie, don't you dare retype it from memory.

🦋 Members 🦋

let's do a vibe check on every single field, one by one, no skipping, no cap:

• dev — reference to the associated struct device. her link to the device world 💖
• label — identifier of the glink edge. that's her name tag at the party 🏷️
• rx_pipe — pipe object for the receive FIFO. incoming mail slot 📬
• tx_pipe — pipe object for the transmit FIFO. outgoing mail slot 📤
• rx_work — worker for handling received control messages. she does the actual work, unlike some people 😭
• rx_lock — protects the rx_queue. bodyguard energy, don't touch 🛡️
• rx_queue — queue of received control messages to be processed in rx_work. the to-do list 📝
• tx_lock — synchronizes operations on the tx fifo. one at a time please, there's a line 🚦
• idr_lock — synchronizes lcids and rcids modifications. protects both, equal treatment, slay ⚖️
• lcids — idr of all channels with a known local channel id. local besties only 💜
• rcids — idr of all channels with a known remote channel id. long-distance besties 🌈
• features — remote features. what the other side can do ✨
• intentless — flag to indicate that there is no intent. not me being intentless 😭🙈
• tx_avail_notify — Waitqueue for pending tx tasks. they wait here, patiently, like me waiting for a text back 💀
• sent_read_notify — flag to check cmd sent or not. did it send? did it not? the suspense 🔥
• abort_tx — flag indicating that all tx attempts should fail. yes, ALL of them. dramatic? maybe. accurate? absolutely 👑

⚠️ heads up bestie: that last one is a real mood-killer — abort_tx literally means every single tx attempt should fail. no exceptions, no partial credit.

👑 SEE ALSO 👑

go read these next, they're all part of the same friend group, fr fr:

• Kernel file ./drivers/rpmsg/qcom_glink_native.c struct glink_defer_cmd(9)
• struct glink_core_rx_intent(9)
• struct glink_channel(9)
• qcom_glink_send_open_req(9)
• qcom_glink_receive_version(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)

⭐ and that's the whole page, bestie! ily, stay hydrated, and remember: this one came to you from ./drivers/rpmsg, dated October 2026, in the one and only struct qcom_glink(9) manpage. periodt. 💅🎀🌸