tpm_cr50_check_locality(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… tpm_cr50_check_locality(9) β€” the Kernel API Manual glow-up

okay so bestie, welcome to tpm_cr50_check_locality(9) ✨ this is the kernel API page for it, and honestly? it's a little one but it's doing its job and we respect it 🫢


🌸 NAME 🌸

tpm_cr50_check_locality β€” literally just verifying that the TPM locality you need is actually active. that's the whole vibe check πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

int tpm_cr50_check_locality (struct tpm_chip *chip , int loc );

no cap, that's the whole signature. she's compact πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • chip β€” a TPM chip. that's it, that's the whole description, she's a chip and we love her 🧚
  • loc β€” the locality you want verified. like, "is this locality active or not" energy ⭐

πŸ”₯ RETURN πŸ”₯

here's what you get back, and it's giving two options only 😭

  • loc β€” Success. yes, it returns the locality value itself on success, iconic behaviour fr fr πŸ‘‘
  • -errno β€” a POSIX error code. the classic "something's off" situation πŸ’€

🌈 SEE ALSO 🌈

the whole friend group, iykyk πŸ’œ

kernel file ./drivers/char/tpm/tpm_tis_i2c_cr50.c and the struct tpm_i2c_cr50_priv_data(9) β€” plus literally all of these:

like, the whole squad showed up to the function's birthday party πŸŽ‚πŸ’–


πŸ’‘ friendly reminder: loc in the RETURN section means the locality value coming back at you β€” don't get it twisted with the loc argument, they're the same name but she's wearing two different outfits okay πŸ’…

and that's the page!! this one lives under ./drivers/char/tpm, dated October 2026, and it's the tpm_cr50_check_locality(9) manual page β€” periodt. go check those localities, bestie, you got this πŸ¦‹βœ¨πŸ’œ

πŸ“¦ where this page comes from