peci_temp_read(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– peci_temp_read(9) β€” kernel API manual, bestie edition πŸ’–

okay so we're diving into the PECI corner of the kernel, and this page is literally about reading the max die temp off a PECI target device 🌑️✨ it's giving thermals, it's giving "how hot is this chip actually" β€” let's go πŸ’…


🌸 NAME 🌸

peci_temp_read β€” read the maximum die temperature from a PECI target device 🫢

✨ SYNOPSIS ✨

int peci_temp_read (struct peci_device *device , s16 *temp_raw );

πŸŽ€ ARGUMENTS πŸŽ€

  • device β€” the PECI device that the request is going to be sent to πŸ“¨ like, this is your target, your main character, the one we're asking about
  • temp_raw β€” where to store the read temperature πŸ“ this is the lil output spot, the container, the place the answer lands

πŸ’œ DESCRIPTION πŸ’œ

It uses the GetTemp PECI command. periodt. that's the whole vibe check β€” GetTemp is the PECI command doing the work here πŸ”₯

⭐ RETURN ⭐

0 if it succeeded πŸŽ‰ β€” anything else means errors, and ngl that's a "guess we're debugging" moment 😭

πŸ¦‹ SEE ALSO πŸ¦‹

go read those too bestie, they're all in the same friend group iykyk πŸ‘‘


πŸ’€ no cap: 0 means slayed, any other value means error β€” don't ignore your return codes, they're telling you something πŸ™ˆ

okay that's the whole page, you ate that πŸŽ€πŸ’– this one lives in ./drivers/peci, and the little vibe stamp at the bottom of the original says October 2026 β€” iconic date, iconic directory, see you in the next manpage bestie 🌈✨🫢

πŸ“¦ where this page comes from