STRUCT PECI_REQUEST(9)

✨ struct peci_request(9) ✨

okay so bestie, welcome to the Kernel API Manual entry for struct peci_request(9) — this is literally the glow-up era of PECI requests and we're gonna get into it 💅

---

🌸 NAME 🌸

struct peci_request — PECI request, the whole vibe, the main character struct 🎀

---

🦋 SYNOPSIS 🦋

struct peci_request {
    struct peci_device *device;
    struct {
      u8 buf[PECI_REQUEST_MAX_BUF_SIZE];
      u8 len;
    } rx, tx;
 };

no cap, that's the whole thing. it's giving "small but does the work" 🫶

---

👑 Members 👑

bestie, these are the fields and you literally cannot skip a single one:

• device — the PECI device to which the request is sent. that's who we're talking to 💌
• rx — RX buffer specific data. the incoming energy 🌈
• rx.buf — RX buffer. literally the buffer where the reply lands 🍓
• rx.len — received data length in bytes. how much actually showed up 📏
• tx — TX buffer specific data. our outgoing energy ✨
• tx.buf — TX buffer. where we put the stuff we're sending 🎀
• tx.len — transfer data length in bytes. how much we're sending out into the world 💫

---

💖 Description 💖

okay so listen: a peci_request represents a request issued by the PECI originator (that's TX, us, the one doing the asking 🫡) and a response received from the PECI responder (that's RX, them, the one doing the answering 😭).

it's literally a whole conversation in a struct. the way that one struct holds both sides of the exchange is lowkey iconic 🔥

---

🌟 SEE ALSO 🌟

iykyk, go check these out too bestie:

• Kernel file ./include/linux/peci.h
• struct peci_controller_ops(9)
• struct peci_controller(9)
• struct peci_device(9)

---

🧚 okay and one last thing before you go — this whole page lives under ./include/linux and it's dated October 2026, so you know exactly where it came from and when. slay, periodt, go read the kernel source bestie 💜👑