__v4l2_devic...vs_until_err(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the Kernel API Manual ✨ β€” this is the page for __v4l2_device_call_subdevs_until_err (the header shows it as __v4l2_devic...vs_until_err(9), love a good truncation πŸ’…).

πŸ’– NAME πŸ’–

__v4l2_device_call_subdevs_until_err β€” calls the specified operation for all subdevs matching the condition. That's the whole vibe: call subdevs until err. Periodt. πŸ’«

πŸŽ€ SYNOPSIS πŸŽ€

The signature, exactly as it appears:

       __v4l2_device_call_subdevs_until_err (v4l2_dev , cond , o , f , args...
       );

πŸ¦‹ ARGUMENTS πŸ¦‹

Here's the cast, bestie 🫢:

  • v4l2_dev β€” the struct v4l2_device owning the sub-devices to iterate over.
  • cond β€” the condition to be match πŸ‘€ (we're keeping the original phrasing, it's giving kernel-speak).
  • o β€” name of the element at struct v4l2_subdev_ops that contains f. Each element there groups a set of operations functions.
  • f β€” operation function that will be called if cond matches. The operation functions are defined in groups, according to each element at struct v4l2_subdev_ops.
  • args β€” arguments for f.

🌸 DESCRIPTION 🌸

If the operation returns an error other than 0 or -ENOIOCTLCMD for any subdevice, then abort and return with that error code; zero otherwise. No cap, that's the whole rule. πŸ’…

⚠️ NOTE ⚠️

bestie, important: subdevs cannot be added or deleted while walking the subdevs list. So don't touch the list mid-walk β€” that's the warning, fr fr πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

Go read these too, iykyk πŸ“š:


cute little sign-off: this page comes from the source spot ./include/media, dated October 2026, and it's the __v4l2_devic...vs_until_err(9) page in the Kernel API Manual β€” mwah, slay, bye bestie πŸ’–βœ¨

πŸ“¦ where this page comes from