Documentation/leds/leds-class-flash.rst

5 Some LED devices provide two modes - torch and flash. In the LED subsystem
6 those modes are supported by LED class (see Documentation/leds/leds-class.rst)
13 registered in the LED subsystem with led_classdev_flash_register function.
16 (see Documentation/ABI/testing/sysfs-class-led-flash)
18 	- flash_brightness
19 	- max_flash_brightness
20 	- flash_timeout
21 	- max_flash_timeout
22 	- flash_strobe
23 	- flash_fault
33 The driver must call the v4l2_flash_init function to get registered in the
34 V4L2 subsystem. The function takes six arguments:
36 - dev:
38 - of_node:
40 - fled_cdev:
42 - iled_cdev:
45 - ops:
49 		defines the source of the flash LED strobe -
55 		enum led_brightness <-> V4L2 intensity conversion in a device
56 		specific manner - they can be used for devices with non-linear
58 - config:
59 	configuration for V4L2 Flash sub-device
66 		available in <linux/led-class-flash.h>,
77 On remove the v4l2_flash_release function has to be called, which takes one
78 argument - struct v4l2_flash pointer returned previously by v4l2_flash_init.
79 This function can be safely called with NULL or error pointer argument.
81 Please refer to drivers/leds/leds-max77693.c for an exemplary usage of the
84 Once the V4L2 sub-device is registered by the driver which created the Media
85 controller device, the sub-device node acts just as a node of a native V4L2
88 Opening the V4L2 flash sub-device makes the LED subsystem sysfs interface
89 unavailable. The interface is re-enabled after the V4L2 flash sub-device