bdisp_hw_get_hv_inc(9)

📦 version 7.3.1, in nixpkgs unstable

💅 bdisp_hw_get_hv_inc(9) — the kernel API manual, but make it make sense

okay so bestie, welcome to the bdisp_hw_get_hv_inc page from the Kernel API Manual ✨ this is a little function from the kernel's driver world, and yes, the NAME section literally just says the name with a dangling dash and no blurb after it, so we're matching that energy fr fr 🎀

✨ NAME ✨

bdisp_hw_get_hv_inc — (and that's it, the manpage really left the description blank, no cap 💀)

🌸 SYNOPSIS 🌸

int bdisp_hw_get_hv_inc (struct bdisp_ctx *ctx , u16 *h_inc , u16 *v_inc );

it's giving "three args, one int, let's go" 🦋

💖 ARGUMENTS 💖

  • ctx — device context 👑 this is the context for the device, the main character of the call
  • h_inc — horizontal increment 🌈
  • v_inc — vertical increment ⭐

🧚 DESCRIPTION 🧚

so what does it actually do? it computes the horizontal & vertical increments — which are the inverse of scale 🫶 that's the whole vibe. increments in, scaling out, iconic behaviour only 💅

🔥 RETURN 🔥

  • 0 on success ✅ that's it, that's the return value, zero means we slayed

🦋 SEE ALSO 🦋

first up, the kernel file this lives in — literally:

Kernel file ./drivers/media/platform/st/sti/bdisp/bdisp-hw.c

and then the whole friend group of related functions, all of them, not skipping a single one 😭:

like, that's the whole squad, go read them too 🫶

okay that's the page!! mwah 💜

this little beauty comes from ./drivers/media/platform/st/st... and it's dated October 2026 — so go forth, compute those increments, and remember: horizontal and vertical, inverse of scale, 0 on success. periodt 💅✨🎀

📦 where this page comes from