__v4l2_ctrl_s_ctrl_int64(9)

📦 version 7.3.1, in nixpkgs unstable

💅 __v4l2_ctrl_s_ctrl_int64 — Kernel API Manual, bestie edition 🎀

okay so real talk, this is the page for __v4l2_ctrl_s_ctrl_int64, straight out of the Kernel API Manual, and honestly? she's lowkey a niche icon. the double-underscore prefix is basically her "do not perceive me unless you know what you're doing" energy. iykyk 💅

✨ NAME ✨

__v4l2_ctrl_s_ctrl_int64 — the unlocked variant of v4l2_ctrl_s_ctrl_int64(). yes bestie, she's the unfenced one, the one that trusts you. 🫶

🌸 SYNOPSIS 🌸

int __v4l2_ctrl_s_ctrl_int64 (struct v4l2_ctrl *ctrl , s64 val );

like, that's the whole signature. int in, int out, and two args to love. ⭐

🦋 ARGUMENTS 🦋

  • ctrl — The control. the actual control we're messing with, the main character of this whole operation 👑
  • val — The new value. the new value we're assigning to it, no cap ✨

💖 DESCRIPTION 💖

so here's the tea 🍓 — this function sets the control's new value safely by going through the control framework. not out here rawdogging struct fields, we're doing it the proper way, periodt.

the important bit, bestie: this function assumes the control's handler is already locked. like, it literally shows up to the party assuming the door's already locked behind you 🔒. that's what lets it be used from within the v4l2_ctrl_ops functions — you're already inside, so you don't need to re-lock, and that's the whole vibe.

and just so we're clear: this function is for 64-bit integer type controls only. do NOT try to sneak a different type in here, it's giving wrong-audience 😭

🌈 SEE ALSO 🌈

the friend group is huge, so buckle up, this is everybody 🫶

like i said. huge friend group. she knows everyone at the function party 🧚

and that's the whole page, bestie, you ate that 💜 this lil beauty lives over in ./include/media, stamped October 2026, and that's the source and version energy right there — so go forth, lock your handler first, and slay 🔥👑

📦 where this page comes from