STRUCT HWTSTAMP_PROVIDER(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct hwtstamp_provider β€” the hwtstamp provider object πŸ’–

okay so bestie, welcome to the struct hwtstamp_provider(9) page β€” this is from the Kernel API Manual, and it's literally the little object that represents a hwtstamp provider. it's giving "small struct, big job" energy ngl πŸŽ€


✨ SYNOPSIS ✨

here's the whole thing laid out, exactly as it lives in the kernel:

struct hwtstamp_provider {
    struct rcu_head rcu_head;
    enum hwtstamp_source source;
    struct phy_device *phydev;
    struct hwtstamp_provider_desc desc;
 };

look at her. four members. no notes. 🫢


🌸 Members 🌸

  • rcu_head β€” the RCU callback that gets used to free the struct. yes, she has a whole lifecycle, we love a self-cleaning queen πŸ’…
  • source β€” the source of the hwtstamp provider (it's an enum hwtstamp_source, so iconic of her).
  • phydev β€” a pointer to the phydev source, and it's specifically for when a PTP is coming from phylib. so if that's your situation? this is your girl πŸ”₯
  • desc β€” the hwtstamp provider description. it's a struct hwtstamp_provider_desc and it does exactly what it says on the tin, no cap.

πŸ¦‹ SEE ALSO πŸ¦‹

  • Kernel file ./include/linux/net_tstamp.h β€” go read it, iykyk
  • struct hwtstamp_provider_desc(9)
  • struct kernel_hwtstamp_config(9)

those two structs are her besties fr fr, go say hi πŸ’œ


πŸ’€ reminder that this page is filed under ./include/linux, so that's where the whole vibe lives. no wander off.

and that's the whole page, bestie β€” written by the folks over in ./include/linux, dated October 2026, and no you can't skip the date, it's part of the lore β­πŸŒˆπŸ’–

πŸ“¦ where this page comes from