HANTRO_DEBUG: MODULE PARAMETER TO CONTROL LEVEL OF DEBUGGING MESSAGES.(9)

🦋 hantro_debug: Module parameter to control level of debugging messages 🦋

okay so bestie, we're in the Kernel API Manual, and this page is all about hantro_debug — the module parameter that controls the level of debugging messages. ✨

the level of debugging messages can be controlled by bits of a module parameter called debug (yep, that's literally its name, she's not being mysterious 💅). the meaning of each particular bit is, like, exactly this:

• bit 0 — global information: mode, size, init, release 🌍
• bit 1 — each run start/result information 🏁
• bit 2 — contents of small controls from userspace 🐣
• bit 3 — contents of big controls from userspace 🐘
• bit 4 — detail fmt, ctrl, buffer q/dq information 🔍
• bit 5 — detail function enter/leave trace information 🚪
• bit 6 — register write/read information 📝

it's giving "pick your debug detail level with bits" and honestly? iconic. 🎀

🌈 SEE ALSO 🌈

• Kernel file ./drivers/media/platform/verisilicon/hantro.h 📁
• struct hantro_irq(9) 👑
• struct hantro_variant(9) 🌸
• enum hantro_codec_mode(9) 🎬
• struct hantro_dev(9) 💻
• struct hantro_ctx(9) 🧠
• struct hantro_fmt(9) 🎞️

and that's the whole page, bestie — mwah 💋 cute little sign-off: this one's source/version is ./drivers/media/platform/veris..., it's dated October 2026, and the manual name is hantro_debug...ng messages.(9). periodt. 🫶