cvs_csi_enable_streams(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cvs_csi_enable_streams(9) β€” the Kernel API Manual glow-up ✨

okay so bestie, you're in the Kernel API Manual and today's main character is cvs_csi_enable_streams(9). it's giving "press play on the bridge" energy and honestly? iconic. let's get into it πŸŽ€


✨ NAME ✨

cvs_csi_enable_streams β€” Start streaming through the bridge. that's it, that's the vibe. it turns the stream ON πŸ”₯


🌸 SYNOPSIS 🌸

int cvs_csi_enable_streams (struct v4l2_subdev *sd , struct
v4l2_subdev_state *state , u32 pad , u64 streams_mask );

copy it exactly like that, no cap, don't touch the spacing, she's perfect the way she is πŸ’–


πŸ¦‹ ARGUMENTS πŸ¦‹

  • sd β€” the Sub-device pointer. literally the sub-device, pointing at stuff 🫢
  • state β€” the Active state. the state that is, yk, active ✨
  • pad β€” the Pad identifier. and bestie, listen, it must be ICVS_CSI_PAD_SOURCE β€” that's not a suggestion, that's the rule πŸ’…
  • streams_mask β€” the Streams to enable. and the tea is: bit 0 supported πŸ‘‘

πŸ’œ DESCRIPTION πŸ’œ

so what does she actually do? buckle up:

she Runtime-resumes the bridge β€” which triggers cvs_runtime_resume to claim CSI-2 link ownership (yes, claiming ownership, main character behavior fr fr). then she fetches the link frequency, programs the MIPI configuration, and forwards the enable request downstream. like a whole little relay race and she wins every leg πŸ†

no skipping steps, okay? resume β†’ fetch β†’ program β†’ forward. the pipeline is the pipeline πŸ’€

πŸ“ RETURN πŸ“

  • 0 on success πŸŽ‰
  • negative errno if it doesn't slay 😭

🌈 SEE ALSO 🌈

go read these next, iykwup (iykyk with Unix pages):


and that's the whole page, bestie 🧚 source living over at ./drivers/media/i2c/cvs, version-dated October 2026 β€” so go stream responsibly, mwah πŸ’‹πŸ’–

πŸ“¦ where this page comes from