STRUCT PECI_DEVICE(9)

💖 NAME 💖 — struct peci_device(9) from the Kernel API Manual

struct peci_device — PECI device. That's the NAME section, bestie, and yes this is the Kernel API Manual page for it — stay with me, the struct lore is lowkey important 💅✨

🌈 SYNOPSIS 🌈

       struct peci_device {
           struct device dev;
           struct {
             u32 x86_vfm;
             u8 peci_revision;
             u8 socket_id;
           } info;
           u8 addr;
           bool deleted;
        };

🌸 Members 🌸

Okay bestie, here's the member-by-member vibe check 👑

• dev — the device object you register the PECI device to in the device model, no cap.
• info — PECI device characteristics, aka the lil' info bundle.
  • info.x86_vfm — the device vendor-family-model. yep, all three in one field, iconic.
  • info.peci_revision — the PECI revision supported by the PECI device.
  • info.socket_id — the socket ID represented by the PECI device.
• addr — the address used on the PECI bus connected to the parent controller.
• deleted — indicates that the PECI device was already deleted. so it's giving "already gone, bestie" 💀

🦋 Description 🦋

A peci_device identifies a single device (i.e. CPU) connected to a PECI bus — one CPU, one lil' main character on the bus 🌟. The behaviour exposed to the rest of the system is defined by the PECI driver managing the device. fr fr, the driver is the one steering the vibe here.

🎀 SEE ALSO 🎀

• Kernel file ./include/linux/peci.h — go read it bestie 📖
• struct peci_controller_ops(9)
• struct peci_controller(9)
• struct peci_request(9)

mwah 💋 this cutie lives under ./include/linux and is dated October 2026, and it's the struct peci_device(9) page — bye bestie, go slay your PECI bus 🫶✨