bdisp_hw_get_inc(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

bdisp_hw_get_inc — okay so bestie, the original literally leaves this blank (just a lonely little dash, no cap 😭), so all we get is the name itself. It's a kernel function in section 9 of the manual, and it lives to hand you back an increment value. That's the whole vibe check. 🦋

✨ SYNOPSIS ✨

int bdisp_hw_get_inc (u32 from , u32 to , u16 *inc );

🎀 ARGUMENTS 🎀

  • from — the input size, literally the size you're coming from, bestie 🫶
  • to — the output size, i.e. the size you're going to ✨
  • inc — the resize increment in 6.10 format, and yes it's a u16 * so it's a pointer, don't come for me 💅

🌸 DESCRIPTION 🌸

It computes the increment — which is the inverse of the scale, iykyk 🔄 — in 6.10 format. That's it. That's the whole function. Short and iconic, main character energy fr fr 👑.

⭐ RETURN ⭐

0 on success 🎉 (that's the only thing listed, so don't go expecting a whole novel of error codes, bestie 🙈).

🔥 SEE ALSO 🔥

Kernel file ./drivers/media/platform/st/sti/bdisp/bdisp-hw.c — that's where the actual source lives, go read it, it's giving homework but make it fun 📚💖

And the whole friend group of related functions, all in section 9:

Heads up bestie 🫶: the original page doesn't spell out anything beyond what's here — no extra warnings, no hidden gotchas, no "oh btw it explodes if you…" notes. So don't invent drama where there isn't any. 💀

And that's a wrap! 🌈 This lil page comes from the kernel API manual, pulled out of ./drivers/media/platform/st/st..., and it's dated October 2026 — yes, a whole future date, we love a time traveler moment ⏰💜. Slay, bye! 🎀

📦 where this page comes from