atcwdt_get_int_timer_type(9)
π atcwdt_get_int_timer_type β the kernel API manual, but make it make sense
okay so bestie, welcome to atcwdt_get_int_timer_type(9) β yes it's a mouthful, yes it's from the Kernel API Manual, and yes I'm gonna walk you through it like we're on FaceTime π«Ά
β¨ NAME β¨
atcwdt_get_int_timer_type β literally just gets you the supported interrupt timer type. that's the whole gig π
πΈ SYNOPSIS πΈ
int atcwdt_get_int_timer_type (struct atcwdt_drv *drv_data );
π ARGUMENTS π
drv_dataβ a pointer to the watchdog driver data structure. like, the driver's whole personality in one struct, and you're handing it over π₯
π¦ DESCRIPTION π¦
so what this function actually does: it goes and tests the writable bits in the IntTime field of the control register π and from that it figures out which interrupt timer type your hardware is out here supporting. it's giving detective energy, ngl. π΅οΈββοΈβ¨
π NOTE π
π¨ bestie, listen to me: this function must only be called when the ATCWDT200 watchdog is disabled. if the watchdog is enabled, this function returns -EBUSY. no cap, it will straight up refuse. so check that watchdog first, okay? π
β RETURN β
0on success π- a negative error code on failure π
π SEE ALSO π
Kernel file ./drivers/watchdog/atcwdt200_wdt.cenum timer_type(9)struct atcwdt_drv(9)atcwdt_get_index(9)atcwdt_get_clock_period(9)atcwdt_get_timeout_params(9)
like, go read those next, iykyk ππ
and that's the whole page, bestie π§ mwah π this little drop came from ./drivers/watchdog, dated October 2026 β iconic of it, honestly. periodt. ππ
π¦ 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