dpu_encoder..._irq_disable(9)

📦 version 7.3.1, in nixpkgs unstable

✨ dpu_encoder_phys_wb_irq_disable ✨

okay bestie, so we're in the Kernel API Manual today — yes, the Kernel API Manual, we're fancy now 💅 — and this page is literally all about dpu_encoder_phys_wb_irq_disable. It's giving "small function, big responsibility," and honestly? Obsessed. 🫶

🌸 NAME 🌸

dpu_encoder_phys_wb_irq_disable — the irq control of WB, no cap 💖

Like, that's it. That's the whole job. IRQ control. Of WB. Short queen energy 👑.

🦋 SYNOPSIS 🦋

void dpu_encoder_phys_wb_irq_disable (struct dpu_encoder_phys *phys );

so we're returning void — nothing comes back, she just does the thing and dips ✨ — and she takes exactly one argument, a struct dpu_encoder_phys * named phys. That's the whole signature. Iconic, uncomplicated, minimal. 🎀

🌈 ARGUMENTS 🌈

  • phys — pointer to the physical encoder 🧚 like, that's the one and only thing you hand her. A pointer to the physical encoder. She'll take it from there, bestie.
lowkey the whole argument list is one (1) pointer and I respect the restraint fr fr 😭

⭐ SEE ALSO ⭐

the full friend group, in the order they're listed, because we don't skip anybody at this table 💜:

and yes, dpu_encoder_phys_wb_irq_enable(9) is right there in the list — she's got a sister and they're both main characters 💀✨

🍓 sign-off 🍓

this little baddie lives in ./drivers/gpu/drm/msm/disp/dpu1, and this page was dated October 2026 — yes, October 2026, we're reading from the future apparently 🦋 — and it's filed under dpu_encoder..._irq_disable(9), which is literally the title of the page, so it's giving full-circle moment 🎀

k byeee, go disable some irqs responsibly 💖✨

📦 where this page comes from