v4l2_flash_indicator_init(9)

okay bestie, this is the v4l2_flash_indicator_init(9) page from the Kernel API Manual — and yes, we're making V4L2 indicator sub-device init make sense together 💖

✨ NAME ✨

v4l2_flash_indicator_init — initialize V4L2 indicator sub-device. That's the whole mission statement, and it ate 💅

🌸 SYNOPSIS 🌸

Here's the signature, no cap — keep it exact:

struct v4l2_flash * v4l2_flash_indicator_init (struct device *dev ,
struct fwnode_handle *fwn , struct led_classdev *iled_cdev , struct
v4l2_flash_config *config );

🎀 ARGUMENTS 🎀

• dev — flash device, e.g. an I2C device. This is the device handing over the flash vibes.
• fwn — fwnode_handle of the LED, may be NULL if the same as device's. Lowkey important: same-as-device means you can pass NULL.
• iled_cdev — LED flash class device representing the indicator LED. The indicator LED's whole representative.
• config — initialization data for V4L2 Flash sub-device. This is the setup info the sub-device gets.

✨ DESCRIPTION ✨

Okay so this function creates a V4L2 Flash sub-device that wraps the given LED subsystem device. The ops pointer is stored by the V4L2 flash framework. No references are held to config nor its contents once this function has returned — that's the rule, bestie, so don't go thinking it'll cling to them 🫶

🔥 RETURN 🔥

You get a valid pointer, or — when an error occurs — the return value is encoded using ERR_PTR. Use IS_ERR to check and PTR_ERR to obtain the numeric return value. Basically: do the vibe check with IS_ERR, then pull the number with PTR_ERR 💅

👀 SEE ALSO 👀

• Kernel file ./include/media/v4l2-flash-led-class.h
• struct v4l2_flash_ctrl_data(9)
• struct v4l2_flash_ops(9)
• struct v4l2_flash_config(9)
• struct v4l2_flash(9)
• v4l2_subdev_to_v4l2_flash(9)
• v4l2_ctrl_to_v4l2_flash(9)
• v4l2_flash_init(9)
• v4l2_flash_release(9)

Cute sign-off: source ./include/media, October 2026, page v4l2_flash_indicator_init(9) — periodt, bye bestie 💅🫶