tpm_chip_alloc(9)

🌸 tpm_chip_alloc(9) 🌸

okay so this is from the Kernel API Manual, and bestie, it's literally about giving birth to a struct tpm_chip 💖 it's short, it's sweet, it's giving "small but mighty" energy, let's go ✨

---

💫 NAME 💫

tpm_chip_alloc — allocate a new struct tpm_chip instance 🫶

like, you're manifesting a whole chip object into existence. main character behavior fr fr 👑

---

✨ SYNOPSIS ✨

struct tpm_chip * tpm_chip_alloc (struct device *pdev , const struct tpm_class_ops *ops );

two args, one return, zero drama. slay 💅

---

🎀 ARGUMENTS 🎀

• pdev — the device your chip is getting associated with 💞 no cap, at this point pdev mst be initialized already, but it does not have to be registered yet. (yes the manpage literally says mst instead of must — typo era, we love her anyway 🙈 the meaning is "must", don't come for me)
• ops — your struct tpm_class_ops instance. that's it. that's the whole vibe check 🦋

---

🌈 DESCRIPTION 🌈

so what actually happens? tpm_chip_alloc allocates a brand new struct tpm_chip instance and assigns it a free device number for it ✨ iconic, honestly.

and here's the part you CANNOT skip: it must be paired with put_device(chip->dev).

⚠️ bestie I'm so serious — if you alloc and don't put_device(chip->dev), that's a leak, that's not the vibe, that's a red flag 🚩 pair them up like matching friendship bracelets or it's over 😭

---

👑 SEE ALSO 👑

kernel file ./drivers/char/tpm/tpm-chip.c — go read the source, iykyk 📖

and the whole friend group:

• tpm_chip_start(9)
• tpm_chip_stop(9)
• tpm_try_get_ops(9)
• tpm_put_ops(9)
• tpm_default_chip(9)
• tpm_dev_release(9)
• tpm_class_shutdown(9)
• tpmm_chip_alloc(9) — yes double-m, that's not a typo on my end, that's literally how it's spelled, keep it exactly like that 💀

---

okay that's the whole page, you ate that 🍓💜 this one lives in ./drivers/char/tpm, dated October 2026, and the page itself is tpm_chip_alloc(9) — mwah, go forth and free your devices, bestie 🧚‍♀️🎀✨