stmp3xxx_wdt_set_timeout(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– stmp3xxx_wdt_set_timeout(9) β€” Kernel API Manual πŸ’–

okay bestie, welcome to the little corner of the kernel docs where we configure the watchdog inside the STMP3xxx RTC ✨

πŸŽ€ NAME πŸŽ€

stmp3xxx_wdt_set_timeout β€” configure the watchdog inside the STMP3xxx RTC πŸ’…

🌸 SYNOPSIS 🌸

void stmp3xxx_wdt_set_timeout (struct device *dev , u32 timeout );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the parent device of the watchdog (= the RTC) 🫢
  • timeout β€” the desired value for the timeout register of the watchdog. 0 disables the watchdog πŸ’€

✨ DESCRIPTION ✨

So the watchdog needs one register and two bits which are in the RTC domain πŸ‘‘. To handle the resource conflict, the RTC driver will create another platform_device for the watchdog driver as a child of the RTC device 🌈.

The watchdog driver is passed the below accessor function via platform_data to configure the watchdog 🧚.

Locking is not needed because accessing SET/CLR registers is atomic πŸ”₯. no cap, that's the whole reason it's chill like that πŸ’…

πŸ‘‘ SEE ALSO πŸ‘‘

  • Kernel file ./drivers/rtc/rtc-stmp3xxx.c πŸ“

that's the whole vibe πŸ’– source/version says ./drivers/rtc, dated October 2026, and the page title is stmp3xxx_wdt_set_timeout(9) β€” byeeeee πŸ«ΆπŸ’…βœ¨

πŸ“¦ where this page comes from