cvs_csi_get_mbus_config(9)
π 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:
csi_set_link_cfg(9)cvs_csi_enable_streams(9)cvs_csi_disable_streams(9)cvs_csi_init_state(9)cvs_csi_set_fmt(9)cvs_csi_notify_bound(9)cvs_csi_notify_unbind(9)cvs_csi_init_controls(9)cvs_csi_parse_firmware(9)cvs_csi_init(9)cvs_csi_remove(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms