pcie_encode_t_power_on(9)

📦 version 7.3.1, in nixpkgs unstable

💅 pcie_encode_t_power_on(9) — from the Kernel API Manual, bestie ✨

Okay so sit down, grab a strawberry 🍓, because we're about to get into pcie_encode_t_power_on, which lives in the Kernel API Manual and is honestly such a little icon. It does exactly one thing and it does it flawlessly. Main character energy, no notes. 👑

🌸 NAME 🌸

pcie_encode_t_power_on — the girl whose whole job is encoding T_POWER_ON into the scale and value fields. That's it. That's the gig. 💅

🦋 SYNOPSIS 🦋

void pcie_encode_t_power_on (u32 t_power_on_us , u8 *scale , u8 *value
);

Like, look at her. Three args, returns nothing, absolutely unbothered. ✨

🎀 ARGUMENTS 🎀

  • t_power_on_us — the T_POWER_ON time, in microseconds. Yes, microseconds. Read the unit, bestie, it's literally in the name. 🙈
  • scale — where the encoded T_POWER_ON Scale gets written. Valid range is 0..2, so like, keep it in that lane fr fr.
  • value — where the encoded T_POWER_ON Value goes. 🫶

💖 DESCRIPTION 💖

So here's the whole vibe — T_POWER_ON is encoded like this:

T_POWER_ON(us) = scale_unit(us) * value

And scale_unit is picked by... you guessed it, scale. The mapping is giving very much:

  • 0: 2us
  • 1: 10us
  • 2: 100us

Now, if t_power_on_us exceeds the maximum representable value, the result gets clamped to the largest encodable T_POWER_ON. Not an error, not a crash — just clamped. She's keeping it cute and staying in range. 😌

Receipts required: see PCIe r7.0, sec 7.8.3.2. Like, that's the source, iykyk. 📚

⭐ SEE ALSO ⭐

Go read the whole friend group, they're all linked and they all ate. 🔥

Okay bye bestie!! 🧚 This little baddie lives over in ./drivers/pci/pcie, dated October 2026 — so like, future iconic 💀✨, and it's pcie_encode_t_power_on(9) forever and always. Periodt. 💜

📦 where this page comes from