cvs_csi_get_mbus_config(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cvs_csi_get_mbus_config(9) β€” like, the CSI-2 bus config page bestie

okay so this is from the Kernel API Manual, and it's literally called cvs_csi_get_mbus_config ✨ β€” no cap, that's the whole name.


πŸŽ€ NAME πŸŽ€

cvs_csi_get_mbus_config β€” provides the current CSI-2 bus configuration. That's it, that's the gig. πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

int cvs_csi_get_mbus_config (struct v4l2_subdev *sd , unsigned int pad ,
struct v4l2_mbus_config *cfg );

like… it takes three things and gives you back an int. iconic behavior tbh 🫢


🌸 ARGUMENTS 🌸

  • sd β€” the sub-device. your main character struct πŸ’…
  • pad β€” the pad index. yes bestie, the index, not the pad itself πŸ™ˆ
  • cfg β€” the returned bus config. this one's an output, so it comes back filled in ✨

πŸ‘‘ DESCRIPTION πŸ‘‘

So what does it actually do? It:

  • fills in the lane ordering and the number of lanes πŸ”₯
  • retrieves the link frequency from the remote entity 🌈

that's the whole vibe check, fr fr πŸ’œ


⭐ RETURN ⭐

Returns 0 on success, or a negative errno if it's not giving 😭


🧚 SEE ALSO 🧚

bestie, go read the kernel file at ./drivers/media/i2c/cvs/v4l2.c β€” it's the moment, iykyk πŸ“

and then these iconic siblings:

they all live in ./drivers/media/i2c/cvs, slay πŸ’€


okay bye bestie, mwah πŸ’‹ β€” this page is dated October 2026 and ships from ./drivers/media/i2c/cvs, so go forth and configure those buses πŸŒΈπŸ¦‹πŸ’–

πŸ“¦ where this page comes from