tpm_cr50_i2c_wait_tpm_ready(9)

📦 version 7.3.1, in nixpkgs unstable

💖 tpm_cr50_i2c_wait_tpm_ready(9) 💖

okay so bestie, welcome to the Kernel API Manual ✨ — this is the page for tpm_cr50_i2c_wait_tpm_ready, and honestly? it's giving "small function, big responsibility." let's get into it 🫶

🌸 NAME 🌸

tpm_cr50_i2c_wait_tpm_ready — literally just wait for the tpm to signal ready, that's the whole vibe 💅

✨ SYNOPSIS ✨

int tpm_cr50_i2c_wait_tpm_ready (struct tpm_chip *chip );

bestie it takes exactly one argument and returns an int, no cap 🧚

🎀 ARGUMENTS 🎀

  • chip — a TPM chip. that's it. that's the argument. it's the chip we're waiting on 👑

🦋 DESCRIPTION 🦋

okay so here's the tea ☕ — this function waits for the completion interrupt if one is available. and if it's not available? no stress, it falls back to a fixed delay so the TPM has time to be ready. either way, we're waiting, we're slaying, we're moving on 💅✨

🌈 RETURN 🌈

  • 0 — success 🎉 iconic, we love to see it
  • -errno — a POSIX error code 😭 so like, something went sideways, and the error is one of the POSIX ones

👑 SEE ALSO 👑

the kernel file lives at ./drivers/char/tpm/tpm_tis_i2c_cr50.c — and it's also friends with struct tpm_i2c_cr50_priv_data(9) 🫶 plus this whole squad:

fr fr go read those too, they're all in the same friend group 💀

k bye bestie, this page came from ./drivers/char/tpm and it's dated October 2026 🌸 — and yes, the header said tpm_cr50_i2c_wait_tpm_ready(9) the whole time, we been knew 💖✨🦋

📦 where this page comes from