pmt_telem_get_next_endpoint(9)

💖 NAME 💖

Okay so this is the pmt_telem_get_next_endpoint(9) page from the Kernel API Manual, and bestie, it does exactly what it says: pmt_telem_get_next_endpoint — get the next device id for a telemetry endpoint ✨

---

🌸 SYNOPSIS 🌸

unsigned long pmt_telem_get_next_endpoint (unsigned long start );

---

🎀 ARGUMENTS 🎀

• start — the starting devid to look from, no cap 💅

---

🦋 DESCRIPTION 🦋

This function can be used in a while loop predicate to retrieve the devid of all available telemetry endpoints. Literally the main-character move for walking the whole endpoint list 🔥

The functions pmt_telem_get_next_endpoint and pmt_telem_register_endpoint can be used inside of the loop to examine endpoint info and register to receive a pointer to the endpoint. That pointer is then usable in the telemetry read calls to access the telemetry data. It’s giving “get the pointer, read the data, slay” 💖

---

🌈 RETURN 🌈

• devid — the devid of the next present endpoint from start ✨
• 0 — when no more endpoints are present after start 🫶

---

👑 SEE ALSO 👑

• Kernel file ./drivers/platform/x86/intel/pmt/telemetry.h
• pmt_telem_register_endpoint(9)
• pmt_telem_unregister_endpoint(9)
• pmt_telem_get_endpoint_info(9)
• pmt_telem_find_and_register_endpoint(9)
• pmt_telem_read(9)
• pmt_telem_read32(9)

---

💖 cute little sign-off: this iconic page comes from the source at ./drivers/platform/x86/intel/pmt, dated October 2026 — mwah, go touch some telemetry 🫶✨🎀