ENUM NVEC_MSG_TYPE(9)

💖 enum nvec_msg_type(9) 💖

okay so bestie, welcome to the Kernel API Manual — this is the page for enum nvec_msg_type, and it's literally just "the type of a message" 🎀 that's the whole NAME, no cap.

---

✨ SYNOPSIS ✨

enum nvec_msg_type {
    NVEC_SYS ,
    NVEC_BAT ,
    NVEC_GPIO ,
    NVEC_SLEEP ,
    NVEC_KBD ,
    NVEC_PS2 ,
    NVEC_CNTL ,
    NVEC_OEM0 ,
    NVEC_KB_EVT ,
    NVEC_PS2_EVT

};

like. look at her. ten little constants in a trench coat 🧥💅

---

🌸 Constants 🌸

• NVEC_SYS — a system request/response 👑
• NVEC_BAT — a battery request/response 🔋
• NVEC_GPIO — -- undescribed -- 🙈 yeah the original just says that, i'm not making stuff up
• NVEC_SLEEP — -- undescribed -- 😴 same energy, no description given
• NVEC_KBD — a keyboard request/response ⌨️
• NVEC_PS2 — a mouse request/response 🖱️
• NVEC_CNTL — a EC control request/response 🎛️
• NVEC_OEM0 — -- undescribed -- 🫥
• NVEC_KB_EVT — an event from the keyboard ⭐
• NVEC_PS2_EVT — an event from the mouse ⭐

no i cannot tell you what NVEC_GPIO, NVEC_SLEEP or NVEC_OEM0 do. the manpage literally hands you -- undescribed -- and walks away 💀 that's the lore, that's all we got.

---

🦋 Description 🦋

so here's the tea: events can be fixed or variable sized. that distinction is useless on other message types, because those are always variable sized. periodt. ✨

---

💜 SEE ALSO 💜

• Kernel file ./drivers/staging/nvec/nvec.h
• enum nvec_event_size(9)
• struct nvec_msg(9)
• struct nvec_chip(9)

go read those next, iykyk 🫶

---

and that's the whole page, bestie 💖 this lil beauty lives at ./drivers/staging/nvec, dated October 2026 — mwah, slay, see u in the next manpage 👑🎀🌈