rtc_timer_remove(9)
β¨ rtc_timer_remove(9) β¨
okay so this is a page straight out of the Kernel API Manual bestie, and it's literally about yeeting a timer off an RTC device. stay with me, it's short and it slays π
πΈ NAME πΈ
rtc_timer_remove β removes a rtc_timer from the rtc_device timerqueue π
π¦ SYNOPSIS π¦
void rtc_timer_remove (struct rtc_device *rtc , struct rtc_timer *timer );
π ARGUMENTS π
rtcβ the rtc device, aka the main character here πtimerβ the timer being removed. bye bestie π«Ά
π DESCRIPTION π
So what it does: it removes a timer onto the rtc device's timerqueue and sets the next alarm event appropriately. yes, the original says "onto" and we're not gonna fight it, we're just gonna relay it fr fr β¨
It also clears the enabled bit on the removed timer. no stale enabled vibes left behind π
β οΈ ngl this one's important: you must hold ops_lock for proper serialization of timerqueue. no cap, don't skip this, it's giving race condition otherwise π
π₯ SEE ALSO π₯
Kernel file ./drivers/rtc/interface.c
rtc_read_next_alarm(9)rtc_handle_legacy_irq(9)rtc_aie_update_irq(9)rtc_uie_update_irq(9)rtc_pie_update_irq(9)rtc_update_irq(9)rtc_irq_set_state(9)rtc_irq_set_freq(9)rtc_timer_enqueue(9)rtc_timer_do_work(9)rtc_read_offset(9)rtc_set_offset(9)
like, the whole rtc friend group honestly π§π
mwah π this lil page lives in ./drivers/rtc and it's dated October 2026 β that's the source and version tea, and that's the whole manual page. go hold that ops_lock and slay β¨π
π¦ 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