cdns_wdt_settimeout(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– cdns_wdt_settimeout πŸ’–

okay so bestie, welcome to the Kernel API Manual ✨ β€” this lil page is all about cdns_wdt_settimeout, and honestly? it's giving "quietly important" energy. it sets a new timeout value for the watchdog device. no cap. πŸ•πŸ¦‹


✨ SYNOPSIS ✨

int cdns_wdt_settimeout (struct watchdog_device *wdd , unsigned int
new_time );

like, it takes a pointer to a watchdog device and an unsigned int, and hands you back an int. simple. iconic. πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • wdd β€” the watchdog device in question. yes, the actual struct watchdog_device *. she's the main character here πŸ‘‘
  • new_time β€” the brand-new timeout value that needs to be set. unsigned int, so keep it positive, bestie πŸ™ˆ

⭐ RETURN ⭐

it returns 0 on success. that's it β€” 0 means we ate and left no crumbs πŸ”₯

ngl, 0 is the only return value documented here, so don't go expecting the full saga of error codes. it's 0 on success, periodt πŸ’€

🌸 DESCRIPTION 🌸

so what does this actually do? it updates the watchdog_device timeout with the new value β€” and that value is the one that gets used when cdns_wdt_start is called. so like, this is the setup step; the starting happens later. the way that just makes sense 🧚

lowkey important detail: this function updates the timeout field, it doesn't start anything by itself. cdns_wdt_start is the one who does the starting, and she'll be using whatever new_time you set here. iykyk πŸ’œ


πŸ¦‹ SEE ALSO πŸ¦‹

like, go read the whole friend group, they're all linked πŸ’–


that's the whole page, bestie β€” short, sweet, and fully documented 🌈 this one lives under ./drivers/watchdog and the date on it is October 2026, so yeah, it's got that fresh timestamp energy ⭐ mwah, go set some timeouts πŸ’…πŸŽ€

πŸ“¦ where this page comes from