__v4l2_ctrl...y_dimensions(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

__v4l2_ctrl_modify_dimensions β€” bestie, it's literally the unlocked variant of v4l2_ctrl_modify_dimensions(). Same energy, except you bring the lock πŸ”“βœ¨

(This whole page lives in the Kernel API Manual, just so you know where you are 🫢)


✨ SYNOPSIS ✨

int __v4l2_ctrl_modify_dimensions (struct v4l2_ctrl *ctrl , u32 dims[V4L2_CTRL_MAX_DIMS] );

πŸŽ€ ARGUMENTS πŸŽ€

  • ctrl β€” the control you're updating. the main character, the one getting a glow-up πŸ’–
  • dims β€” the control's brand-new dimensions. new size, who dis 🌸

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so this function updates the dimensions of an array control on the fly β€” like changing your whole aesthetic mid-semester, no cap πŸ”₯ The elements of the array are reset to their default value, even if the dimensions are unchanged. yes, even then. it's giving "fresh start, no exceptions" πŸ’€

An error is returned if dims is invalid for this control. invalid dims? not today, bestie πŸ™ˆ

⚠️ important one: the caller is responsible for acquiring the control handler mutex on behalf of __v4l2_ctrl_modify_dimensions. that's you. you're the lock-holder. periodt πŸ’…

πŸ’€ NOTE πŸ’€

calling this function when the same control is used in pending requests is untested 😭 It should work β€” a request with the wrong size of the control will drop that control silently β€” but it will be very confusing. like, "technically fine but emotionally devastating" energy. ngl, don't do this to yourself 🫠


🌈 SEE ALSO 🌈


and that's the whole page, bestie, you ate that πŸ“ This lil drop comes to you straight from ./include/media, dated October 2026 β€” so go forth, hold that mutex, and slay πŸ’œπŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from