xvip_enum_mbus_code(9)

🌸 xvip_enum_mbus_code(9) 🌸

hiii bestie 💖 welcome to the Kernel API Manual page for xvip_enum_mbus_code(9) — yes, the manual name is folded in near the top like a little name tag, and we are being cute about it ✨

---

🎀 NAME 🎀

xvip_enum_mbus_code — Enumerate the media format code. That's the whole assignment, and it ate 💅

---

🦋 SYNOPSIS 🦋

okay so here's the exact vibe, no edits, no cap:

int xvip_enum_mbus_code (struct v4l2_subdev *subdev , struct
v4l2_subdev_state *sd_state , struct v4l2_subdev_mbus_code_enum *code );

---

💜 ARGUMENTS 💜

• subdev — V4L2 subdevice. This is the subdevice in question, the main character of this call 🫶
• sd_state — V4L2 subdev state. The state it's carrying around, lowkey important.
• code — returning media bus code. This is the returning media bus code spot — it's giving output-parameter energy 💫

---

🌈 DESCRIPTION 🌈

okay so xvip_enum_mbus_code() enumerates the media bus code of the subdevice. It returns the corresponding pad format code. Simple enough, right? 💅

but listen: this function only works for subdevices with fixed format on all pads. Subdevices with multiple format should have their own function to enumerate mbus codes — that's the rule, and we respect it, periodt 👑

---

⭐ RETURN ⭐

• 0 if the media bus code is found — slay ✅
• -EINVAL if the format index is not valid — not slay, but very clear 😭

---

🧚 SEE ALSO 🧚

like, go look at these too, bestie:

• Kernel file ./drivers/media/platform/xilinx/xilinx-vip.c
• xvip_get_format_by_code(9)
• xvip_get_format_by_fourcc(9)
• xvip_of_get_format(9)
• xvip_set_format_size(9)
• xvip_clr_or_set(9)
• xvip_clr_and_set(9)
• xvip_enum_frame_size(9)

---

mwah 💋 this little page comes from ./drivers/media/platform/xilinx, dated October 2026, and it's the xvip_enum_mbus_code(9) manual page — byeee 🎀✨