dp83tg720_ge..._update_time(9)

💅 dp83tg720_ge..._update_time — from the Kernel API Manual (9), bestie

Okay so real talk, this one lives in the kernel API manual, section 9, and the whole vibe is "when do we check on the PHY again?" That's it. That's the function. Let's get into it 🫶

---

✨ NAME ✨

dp83tg720_get_next_update_time — literally just returns the next polling interval for the PHY state 🌸

---

🎀 SYNOPSIS 🎀

unsigned int dp83tg720_get_next_update_time (struct phy_device *phydev );

Yep, that's the whole signature. It hands you back an unsigned int and it wants exactly one thing. Iconic minimalism. 💅

---

🌈 ARGUMENTS 🌈

• phydev — a pointer to the struct phy_device structure. That's your PHY. Your little guy. Point at it and this function does its thing ✨

---

🦋 DESCRIPTION 🦋

So what's it actually doing? It implements adaptive polling interval logic — and the two things that logic depends on are:

• the link state 🔥
• the downtime duration ⏳

That's the whole tea. And for the full tea, the manpage itself says: see the "2. Polling-Based Link Detection and IRQ Support" section at the top of this file for details. So if you want the deep lore, go read the top of the file, iykyk 👑

---

⭐ RETURN ⭐

It returns the time (in jiffies) until the next poll — so like, "hey bestie, come back and check on me in this many jiffies" 🕐

No cap, the unit is jiffies. Not seconds. Not milliseconds. Jiffies. Do not come at me with milliseconds 🙈

---

💜 SEE ALSO 💜

• Kernel file ./drivers/net/phy/dp83tg720.c
• dp83tg720_update_stats(9)
• dp83tg720_cable_test_start(9)
• dp83tg720_cable_test_get_status(9)

All of these are your little friend group, go say hi 🧚

---

✨ and that's the whole page, bestie ✨

Cute little sign-off from the source: this one's filed under ./drivers/net/phy, dated October 2026, and titled dp83tg720_ge..._update_time(9) — because even manpage footers deserve main character energy 👑🎀💖