STRUCT PPE_DEVICE(9)

🎀 NAME 🎀

struct ppe_device — literally the private data for a PPE device, bestie. (This page lives in the Kernel API Manual, iykyk 💅)

---

✨ SYNOPSIS ✨

struct ppe_device {
    struct device *dev;
    struct regmap *regmap;
    unsigned long clk_rate;
    unsigned int num_ports;
    struct dentry *debugfs_root;
    unsigned int num_icc_paths;
    struct icc_bulk_data icc_paths[];
};

---

🌸 Members 🌸

okay so here's the whole cast, no cap, every single one of them:

• dev — the PPE device structure. the main character, honestly 🫶
• regmap — the PPE register map. it's giving "where all the bits live" ✨
• clk_rate — the PPE clock rate. tick tock, queen 💅
• num_ports — how many PPE ports there are. gotta count 'em 🍓
• debugfs_root — the debugfs root entry. lowkey iconic for poking around 🙈
• num_icc_paths — the number of interconnect paths. yes, we're counting these too 🦋
• icc_paths — the interconnect path array. that [] at the end? flexible array member, she's that girl 🌈

---

👑 Description 👑

So <purple>PPE device</purple> is the instance of PPE hardware, and the way it works is it's used to configure PPE packet process modules — like BM (buffer management), QM (queue management), and the scheduler. That's the whole vibe. it's the actual hardware instance you're holding onto, and it's what you pass around when you need to go configure stuff. periodt 💖

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/net/ethernet/qualcomm/ppe/ppe.h — go read it, bestie, it's right there 🧚

---

fr fr, every member above is a real field, don't go renaming any of them 😭 the header file is the source of truth.

---

okay that's the whole page, bestie!! this came out of ./drivers/net/ethernet/qualcom... and it's dated October 2026 — so like, keep it in your notes, mwah 💋💜

struct ppe_device(9) — slay, you're done. 👑✨