v4l2_fwnode_..._alloc_parse(9)

💫 v4l2_fwnode_..._alloc_parse(9) — the Kernel API Manual ✨

okay bestie, welcome to the Kernel API Manual for v4l2_fwnode_..._alloc_parse(9) — like, the iconic little function name, iykyk 🌈. this page is the whole vibe check on it, so grab a lil beverage and let's go 💅

---

✨ NAME ✨

v4l2_fwnode_endpoint_alloc_parse — parse all fwnode node properties. fr fr, all of them, not just a lil taste 🍓

💖 SYNOPSIS 💖

int v4l2_fwnode_endpoint_alloc_parse (struct fwnode_handle *fwnode ,
struct v4l2_fwnode_endpoint *vep );

🎀 ARGUMENTS 🎀

• fwnode — pointer to the endpoint's fwnode handle. may be NULL, bestie, don't panic 🙈
• vep — pointer to the V4L2 fwnode data structure. she's the main character of this whole operation 👑

🌸 DESCRIPTION 🌸

so this function parses the V4L2 fwnode endpoint specific parameters from the firmware. literally her whole job 💅

there are two ways to use this function, and honestly both are valid:

1. let it obtain the type of the bus — do this by setting the vep.bus_type field to V4L2_MBUS_UNKNOWN
2. specify the bus type explicitly — set it to one of the enum v4l2_mbus_type types

when vep.bus_type is V4L2_MBUS_UNKNOWN, the function will use the "bus-type" property to determine the type when it is available. but heads up: the caller is responsible for validating the contents of the vep.bus_type field after the call returns 👀

as a deprecated functionality to support older DT bindings without "bus-type" property for devices that support multiple types — if the "bus-type" property does not exist, the function will attempt to guess the type based on the endpoint properties available. NEVER RELY ON GUESSING THE BUS TYPE IN NEW DRIVERS OR BINDINGS. like, for real, do not. that's the warning, bestie 🚨

it's also possible to set vep.bus_type corresponding to an actual bus. in this case the function will only attempt to parse properties related to this bus, and it will return an error if the value of the "bus-type" property corresponds to a different bus. it's giving "you asked for one thing but the firmware said another" energy 😭

the caller is required to initialise all fields of vep, either with explicitly values, or by zeroing them. all of them. every single one. don't skip any, ngl ✨

the function does not change the V4L2 fwnode endpoint state if it fails. so like, no messy aftermath if things go wrong, we love that for us 🫶

v4l2_fwnode_endpoint_alloc_parse has two important differences to v4l2_fwnode_endpoint_parse — and these are lowkey important okay:

1. it also parses variable size data.
2. the memory it has allocated to store the variable size data must be freed using v4l2_fwnode_endpoint_free when no longer needed.

🚨 like, actually free it. don't leave that memory hanging, bestie. that's a memory leak and it's not cute 💀

⭐ RETURN ⭐

• 0 on success 🎉
• a negative error code on failure, specifically:
  • -ENOMEM on memory allocation failure 😭
  • -EINVAL on parsing failure 🙈
  • -ENXIO on mismatching bus types 💀
  • -EPROBE_DEFER on NULL fwnode 👑

🦋 SEE ALSO 🦋

okay this list is long but we're doing all of it because every reference matters periodt 💅

• Kernel file ./include/media/v4l2-fwnode.h
• struct v4l2_fwnode_endpoint(9)
• V4L2_FWNODE_PROPERTY_UNSET(9)
• enum v4l2_fwnode_orientation(9)
• struct v4l2_fwnode_device_properties(9)
• struct v4l2_fwnode_link(9)
• enum v4l2_connector_type(9)
• struct v4l2_connector_link(9)
• struct v4l2_fwnode_connector_analog(9)
• struct v4l2_fwnode_connector(9)
• enum v4l2_fwnode_bus_type(9)
• v4l2_fwnode_endpoint_parse(9)
• v4l2_fwnode_endpoint_free(9)
• v4l2_fwnode_parse_link(9)
• v4l2_fwnode_put_link(9)
• v4l2_fwnode_connector_free(9)
• v4l2_fwnode_connector_parse(9)
• v4l2_fwnode_connector_add_link(9)
• v4l2_fwnode_device_parse(9)

---

and that's the page, bestie!! 🥳 like, go forth and parse those fwnode node properties responsibly 💖 this lil manual page lives in ./include/media and it's dated October 2026 — so like, future vibes only ✨🦋🫶 slay!! 👑