peci_ep_pci_local_read(9)

🌸 peci_ep_pci_local_read(9) 🌸

okay so bestie, welcome to the Kernel API Manual — section 9 ofc, this is the driver-adjacent girlie zone 💅

---

✨ NAME ✨

peci_ep_pci_local_read — read a 32-bit memory location using a raw address, no cap 🫶

---

🦋 SYNOPSIS 🦋

int peci_ep_pci_local_read (struct peci_device *device , u8 seg , u8 bus
, u8 dev , u8 func , u16 reg , u32 *data );

like. that's a lot of arguments and she's literally serving them all 💀 but it's fine, we go through every single one below 👇

---

🎀 ARGUMENTS 🎀

• device — the PECI device that this request is gonna be sent to. she's the main character, everyone else is just supporting cast 💖
• seg — PCI segment
• bus — bus
• dev — device
• func — function
• reg — register
• data — where the read data goes to live. this is the lil home for your result 🏠✨

ngl, bus, dev, func and reg are giving "the manpage gave up explaining" energy, but that's literally what it says, so we're keeping it exactly like that 🙈

---

💜 DESCRIPTION 💜

So she's like peci_pci_local_read, but — and this is the iconic part — she uses the RdEndpointConfig PECI command instead 🔥 same vibes, different command, iykyk.

---

⭐ RETURN ⭐

• 0 if it succeeded 🎉
• other values in case of errors 😭 (yes, that's all it says, she's mysterious like that)

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/peci/cpu.c
• peci_temp_read(9)
• peci_pcs_read(9)
• peci_pci_local_read(9)
• peci_mmio_read(9)

go read those next, bestie, they're all in ./drivers/peci and they're all slay 👑

---

that's the whole page, periodt. she lives in ./drivers/peci, she's dated October 2026, and this lil group chat was brought to you by the Kernel API Manual 💅🧚💜