bdisp_hw_get_op_cfg(9)

📦 version 7.3.1, in nixpkgs unstable

💅 bdisp_hw_get_op_cfg(9) — a Kernel API Manual moment

okay so bestie, we're in the Kernel API Manual today and this one is a little function with big main-character energy. It lives its life down in the ST/STI bdisp hardware driver, and it's here to look at what the blitter is about to do and set up the scaling math for it. Let's get into it 🫶

✨ NAME ✨

bdisp_hw_get_op_cfg —

and honestly? the description box is empty. nothing. a blank. the manpage said "no thoughts, head empty" and moved on. so the name is the whole vibe, iykyk 💀

🦋 SYNOPSIS 🦋

int bdisp_hw_get_op_cfg (struct bdisp_ctx *ctx , struct bdisp_op_cfg *c );

that's it. two pointers in, one int out. short and iconic 👑

🎀 ARGUMENTS 🎀

  • ctx — the device context. this is the whole situation, the state of the world, the main character of the call 🌈
  • c — the operation configuration. this is where the info about the operation lives so the function can peek at it and do its thing 💖

🌸 DESCRIPTION 🌸

so what does it actually do? it checks which blitter operations are expected, and then it sets the scaling increments. that's the whole job. no cap 🔥

like, it looks at what the blitter is being asked to do and then does the little scaling-increment setup that goes with it. lowkey important, highkey underrated ✨

⭐ RETURN ⭐

0 on success. that's the return, that's the whole list, one value, slay 🎀

💜 SEE ALSO 💜

the kernel file in question, living its best life at:

  • ./drivers/media/platform/st/sti/bdisp/bdisp-hw.c

and its whole friend group, the other bdisp functions:

ngl, this page is short, but every single one of those refs matters — go read the squad if you're doing bdisp things fr fr 🫶

okay that's the whole page bestie, and before you go — credits where credits are due: this one comes from ./drivers/media/platform/st/st... and it's dated October 2026, and yeah, the footer's out here signing off as bdisp_hw_get_op_cfg(9) like the icon it is 💅🌸 bye!

📦 where this page comes from