hte_push_ts_ns(9)

💖 hte_push_ts_ns(9) — like, the Kernel API Manual page, but fun 💖

okay so bestie, we're in the Kernel API Manual today and this one is honestly such a serve — it's the little function that pushes timestamp data around in nanoseconds ⏱️✨. Yes, nanoseconds. She's precise. She's iconic. Let's get into it 🎀

---

✨ NAME ✨

hte_push_ts_ns — push timestamp data in nanoseconds 💅

---

🦋 SYNOPSIS 🦋

int hte_push_ts_ns (const struct hte_chip *chip , u32 xlated_id , struct
hte_ts_data *data );

that's the whole vibe right there, no cap 🔥

---

🌸 ARGUMENTS 🌸

• chip — the HTE chip 🫶. It gets used during the registration, that's its whole moment.
• xlated_id — the entity id, and this one's understood by both the subsystem and the provider (collab of the century honestly 👑). You get it from the xlate callback during the request API.
• data — timestamp data 📊. That's it, that's the arg.

---

💜 DESCRIPTION 💜

So the provider uses this to push timestamp data. That's the whole job 🎯. She pushes. Timestamps happen. Nanoseconds. Live, laugh, love 😌✨.

---

🌈 RETURN 🌈

• 0 on success 🥳
• or a negative error code on failure 😭 (we don't love that for us, but it happens)

---

🧚 SEE ALSO 🧚

go read the kernel file ./drivers/hte/hte.c first, fr fr — then these besties:

• struct hte_ts_info(9)
• struct hte_device(9)
• hte_ts_put(9)
• hte_disable_ts(9)
• hte_enable_ts(9)
• of_hte_req_count(9)
• hte_ts_get(9)
• hte_request_ts_ns(9)
• devm_hte_request_ts_ns(9)
• hte_init_line_attr(9)
• hte_get_clk_src_info(9)
• devm_hte_register_chip(9)

like, a whole friend group 💖🦋🌸

---

💀 reminder bestie: failure gives you a negative error code, not just any old error code. negative. clock it.

---

okay and that's a wrap on this page! 🎀 she lives in ./drivers/hte and the docs stamped her October 2026 — mwah, see you in the next one, periodt 💅✨🫶