STRUCT QTS_HDR(9)

💖 struct qts_hdr(9) 💖

okay so bestie, welcome to the Kernel API Manual — this one's a tiny little struct from the QAIC timesync world and honestly it's giving backstage pass energy. Let's get into it 🎀

---

✨ NAME ✨

struct qts_hdr — the Timesync message header structure. yeah. it's a header. for timesync messages. it's literally in the name and it ate 💅

---

🌸 SYNOPSIS 🌸

here's the whole thing, no cap, copy-paste exact:

struct qts_hdr {
    __le16 signature;
    __le16 reserved_1;
    u8 reserved_2;
    u8 msg_type;
    __le16 reserved_3;
 };

look at her. five fields. compact. iconic. main character energy 👑

---

🦋 Members 🦋

okay let's meet the cast one by one 🫶

• signature — a unique signature that identifies the timesync message. it's basically the vibe check for the message — that's how you know it's this kind of message and not some random imposter 💀
• reserved_1 — reserved for future use. it's a __le16. it's just sitting there, chilling, waiting for its moment. we respect the hustle 🙈
• reserved_2 — reserved for future use again, but this one's a u8. shorter king. still reserved. still valid. ✨
• msg_type — the sub-type of the timesync message. this little u8 is the one that actually tells you what kind of timesync message you're looking at. the drama. the specificity. obsessed 😭
• reserved_3 — reserved for future use, __le16, third and final reserved field. trio complete. slay 🌈

ngl, three reserved fields is a lot of "we'll deal with it later" energy and I love that for her 💖

---

🧚 SEE ALSO 🧚

• Kernel file ./drivers/accel/qaic/qaic_timesync.c
• struct qts_timeval(9)
• struct qts_host_time_sync_msg_data(9)
• struct mqts_dev(9)

go read the friends, they're all linked together, it's a whole friend group fr fr 🫶

---

aaaand that's the page babes 💜 — brought to you by the fine folks over in ./drivers/accel/qaic, dated October 2026. go forth and sync your times, periodt ⭐🔥