hte_ts_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… hte_ts_get(9) β€” like, the Kernel API Manual entry you actually wanna read

okay so bestie, welcome to hte_ts_get(9) from the Kernel API Manual β€” yes, that manual β€” and no cap, this one is short and sweet. It's the little function that sets up your HTE descriptor before anything else gets to touch it. Let's go πŸŽ€


✨ NAME ✨

hte_ts_get β€” the function to initialize and obtain HTE desc. literally its whole job πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

int hte_ts_get (struct device *dev , struct hte_ts_desc *desc , int
index );

🌸 ARGUMENTS 🌸

  • dev β€” the HTE consumer/client device 🫢 it's used in case of parsing the device tree node, iykyk.
  • desc β€” a pre-allocated timestamp descriptor. pre-allocated, bestie, that part is on you πŸ’€
  • index β€” this index is used as an index to parse line_id from the device tree node if the node is present ✨.

πŸ’œ DESCRIPTION πŸ’œ

so the way this works: hte_ts_get initializes the consumer-provided HTE descriptor. that's the whole vibe check πŸ’…

if the consumer has a device tree node, then index is used to parse the line id and other details from it 🌈.

🚨 real talk: the function needs to be called before using any request APIs. like, before. not after, not "eh, somewhere in the vicinity." before. periodt πŸ”₯

πŸ”’ CONTEXT πŸ”’

Holds mutex lock ⭐ β€” yes queen, it's locking, be aware of that when you're calling it from wherever you're calling it from πŸ™ˆ.


πŸŽ€ RETURN πŸŽ€

Returns 0 on success or a negative error code on failure 😭 (check it, bestie, don't just vibe past the return value).


πŸ‘‘ SEE ALSO πŸ‘‘


and that's the page, bestie!! 🧚 from ./drivers/hte, dated October 2026 β€” mwah πŸ’‹ go forth and get those timestamps πŸ’–βœ¨πŸ“

πŸ“¦ where this page comes from