dev_get_hwtstamp_phylib(9)

💖 dev_get_hwtstamp_phylib — like, the whole vibe ✨

okay so real talk, bestie: this is a page from the Kernel API Manual, section 9 (the kernel-functions girlies 🧚), and the star of the show is dev_get_hwtstamp_phylib. Get into it.

---

🌸 NAME 🌸

dev_get_hwtstamp_phylib — literally the function that gets you the hardware timestamping settings of a NIC, or of a phylib PHY that's attached to it. no cap, that's the whole job 🫶

---

🎀 SYNOPSIS 🎀

int dev_get_hwtstamp_phylib (struct net_device *dev , struct kernel_hwtstamp_config *cfg );

---

🦋 ARGUMENTS 🦋

• dev — the network device in question. your NIC, your fave, the main character 🎬
• cfg — the timestamping configuration structure. this is where the settings live, and it's what you're here for 💅

---

⭐ DESCRIPTION ⭐

It's a helper for calling the default hardware provider timestamping. that's it, that's the function. short and iconic, lowkey💜

---

🙈 NOTE 🙈

okay so this part matters, don't skim it:

phy_mii_ioctl only handles SIOCSHWTSTAMP — not SIOCGHWTSTAMP. but plot twist: phydev->mii_ts has both hwtstamp_get and hwtstamp_set methods, so it's giving options ✨

so for phylib, this will return -EOPNOTSUPP only if hwtstamp_get is not implemented, for now. which is still more accurate than letting the netdev handle the GET request. fr fr, accuracy ate 💀

---

🔥 SEE ALSO 🔥

• Kernel file ./net/core/dev_ioctl.c
• dev_set_hwtstamp_phylib(9)
• dev_load(9)
• dev_ioctl(9)

---

ngl bestie, if you're poking at timestamps and it's throwing -EOPNOTSUPP at you, check whether hwtstamp_get is even implemented. that's the whole tea ☕

---

and that's the page!! 🍓 courtesy of the kernel file ./net/core, dated October 2026 — ily, go timestamp something 💖🌈👑