omap_rproc_watchdog_isr(9)
π NAME π
okay so bestie, this is the omap_rproc_watchdog_isr(9) page from the Kernel API Manual πβ¨ and it's literally the watchdog ISR handler for a remoteproc device.
omap_rproc_watchdog_isr - Watchdog ISR handler for remoteproc device π
β¨ SYNOPSIS β¨
irqreturn_t omap_rproc_watchdog_isr (int irq , void *data );
π ARGUMENTS π
irqβ IRQ number associated with a watchdog timer π₯dataβ IRQ handler data π«Ά
π¦ DESCRIPTION π¦
okay so this ISR routine is the one running the required necessary low-level code to acknowledge a watchdog timer interrupt, no cap π«Ά. a rproc can have multiple watchdog timers associated with it (like IPUs which have 2 watchdog timers, one per Cortex M3/M4 core), so a lookup has to be performed to identify the timer to acknowledge its interrupt. it's giving "which timer is this? bestie, we need to know" π
the function also invokes rproc_report_crash to report the watchdog event to the remoteproc driver core, to trigger a recovery. so it's not just a vibe check β it reports the watchdog event and kicks off recovery π₯ periodt.
πΈ RETURN πΈ
IRQ_HANDLED on success, otherwise IRQ_NONE π
π SEE ALSO π
the Kernel file is ./drivers/remoteproc/omap_remoteproc.c π«Ά and the whole friend group is:
struct omap_rproc_boot_data(9)struct omap_rproc_mem(9)struct omap_rproc_timer(9)struct omap_rproc(9)struct omap_rproc_mem_data(9)struct omap_rproc_dev_data(9)omap_rproc_request_timer(9)omap_rproc_start_timer(9)omap_rproc_stop_timer(9)omap_rproc_release_timer(9)omap_rproc_get_timer_irq(9)omap_rproc_ack_timer_irq(9)omap_rproc_enable_timers(9)omap_rproc_disable_timers(9)omap_rproc_mbox_callback(9)omap_rproc_write_dsp_boot_addr(9)omap_rproc_da_to_va(9)
sending all my love from ./drivers/remoteproc, dated October 2026 β omap_rproc_watchdog_isr(9) from the Kernel API Manual, out π
β¨
π¦ 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