peci_mmio_read(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– peci_mmio_read (9) β€” Kernel API Manual, but make it slay πŸ’–

okay so bestie, welcome to the peci_mmio_read page ✨ this is a kernel API manual page, and it's genuinely so useful β€” let me put you on real quick 🫢


🌸 NAME 🌸

peci_mmio_read β€” read a 32-bit memory location using a 64-bit bar offset address πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

int peci_mmio_read (struct peci_device *device , u8 bar , u8 seg , u8
       bus , u8 dev , u8 func , u64 address , u32 *data );

literally that's the whole signature, keep it exactly like that, no cap πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • device β€” the PECI device that this request is going to be sent to πŸ“¨
  • bar β€” PCI bar
  • seg β€” PCI segment
  • bus β€” bus
  • dev β€” device
  • func β€” function
  • address β€” the 64-bit MMIO address
  • data β€” where you store the read data 🏠

✨ DESCRIPTION ✨

So what does it actually do? It uses the RdEndpointConfig PECI command. that's the vibe. that's the whole description. iconic of it honestly πŸŽ€


πŸ’œ RETURN πŸ’œ

  • 0 if it succeeded πŸŽ‰
  • other values in case of errors 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/peci/cpu.c, plus these little besties:


🫢 quick reminder bestie: every flag, arg, value, and path above is exactly as it appears in the real page β€” no ✨creative liberties✨ taken with the technical bits πŸ’…

and that's the whole page, fr fr πŸ¦‹ this one lives in ./drivers/peci and its date stamp is October 2026 β€” and remember, it's peci_mmio_read(9), the main character of its own footer πŸ’– matter of fact, go read peci_temp_read(9) next, iykyk πŸ”₯

πŸ“¦ where this page comes from