vpu_wdt_reg_handler(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ vpu_wdt_reg_handler(9) πŸŽ€

okay so bestie, welcome to the vpu_wdt_reg_handler(9) page from the Kernel API Manual πŸ’– this one is short, iconic, and all about registering a VPU watchdog handler. periodt.


✨ NAME ✨

vpu_wdt_reg_handler β€” register a VPU watchdog handler πŸ›‘οΈ

🌸 SYNOPSIS 🌸

int vpu_wdt_reg_handler (struct platform_device *pdev , void *priv ,
void *priv , enum rst_id id );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • pdev β€” VPU platform device vpu_wdt_reset_func: the callback reset function.
  • priv β€” the private data for reset function πŸ’œ
  • priv β€” the private data for reset function πŸ’œ yep, it shows up twice, bestie β€” keeping both exactly as listed.
  • id β€” reset id πŸ†”

πŸ”₯ DESCRIPTION πŸ”₯

Register a handler performing own tasks when vpu reset by watchdog. That's the whole vibe: when the VPU gets reset by the watchdog, this handler gets to do its own tasks. slay. πŸ’…

🫢 RETURN 🫢

Return 0 if the handler is added successfully, otherwise it is failed. So 0 is the success case; otherwise it is failed 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/media/platform/mediatek/vpu/mtk_vpu.h:

🫢 cute sign-off: source/version situation is ./drivers/media/platform/media..., dated October 2026, and the page is vpu_wdt_reg_handler(9). bye bestie πŸ’–
πŸ“¦ where this page comes from