stmp3xxx_wdt_set_timeout(9)
π 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.0disables 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms