v4l2_get_active_data_lanes(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, welcome to the Kernel API Manual β€” this page is serving v4l2_get_active_data_lanes, aka the function that gets the number of active data lanes from the driver. no cap, that's literally the whole name vibe. πŸ’…βœ¨


πŸŽ€ SYNOPSIS πŸŽ€

here's the signature, character for character, bestie:

int v4l2_get_active_data_lanes (const struct media_pad *pad , unsigned
int max_data_lanes );

🌸 ARGUMENTS 🌸

  • pad β€” the transmitter's media pad. πŸ“‘
  • max_data_lanes β€” the maximum number of active data lanes supported by the MIPI CSI link in hardware. πŸ”₯

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so the whole point of this function is obtaining the number of data lanes that are actively being used by the driver for a MIPI CSI-2 device on a given media pad. that's the main character energy of it. 🌈

and where does that info come from? it's derived from a mbus_config fetched from a device driver using the get_mbus_config v4l2_subdev pad op. periodt. it's giving β€œask the driver nicely and read the mbus config” πŸ’–


⭐ RETURN ⭐

here's the vibe check on what comes back:

  • >0 β€” Number of active data lanes. πŸ‘‘
  • -EINVAL β€” Number of active data lanes is invalid, as it exceeds the maximum supported data lanes. 🚨 not the slay result, bestie 🚨

πŸ’œ SEE ALSO πŸ’œ

okay the Kernel file is ./include/media/v4l2-common.h, and the whole reference squad is:


mwah πŸ’‹ this page's source is ./include/media, it's dated October 2026, and the page version is v4l2_get_active_data_lanes(9) β€” bye bestie! πŸŽ€πŸ«Ά

πŸ“¦ where this page comes from