What:		/sys/class/leds/<led>/brightness
Date:		March 2006
KernelVersion:	2.6.17
Contact:	Richard Purdie <rpurdie@rpsys.net>
Description:
		Set the brightness of the LED.

		Most LEDs don't have hardware brightness support, so will
		just be turned on for non-zero brightness settings.

		.. Note::

		  For multicolor LEDs, writing to this file will update all
		  LEDs within the group to a calculated percentage of what
		  each color LED intensity is set to.

		  The percentage is calculated for each grouped LED via
		  the equation below::

		    led_brightness = brightness * multi_intensity/max_brightness

		  For additional details please refer to
		  Documentation/leds/leds-class-multicolor.rst.

		The value is between 0 and /sys/class/leds/<led>/max_brightness
		and is represented by as a decimal.

		Writing 0 to this file clears active trigger.

		Writing non-zero to this file while trigger is active changes the
		top brightness trigger is going to use, unless the current
		trigger is offloaded to hardware (in which case writing any
		value will deactivate the trigger).



What:		/sys/class/leds/<led>/max_brightness
Date:		March 2006
KernelVersion:	2.6.17
Contact:	Richard Purdie <rpurdie@rpsys.net>
Description:
		Maximum brightness level for this LED, default is 255 (LED_FULL).

		If the LED does not support different brightness levels, this
		should be 1.

What:		/sys/class/leds/<led>/brightness_hw_changed
Date:		January 2017
KernelVersion:	4.11
Description:
		Last hardware set brightness level for this LED. Some LEDs
		may be changed autonomously by hardware/firmware. Only LEDs
		where this happens and the driver can detect this, will have
		this file.

		This file supports poll() to detect when the hardware changes
		the brightness.

		Reading this file will return the last brightness level set
		by the hardware, this may be different from the current
		brightness. Reading this file when no hw brightness change
		event has happened will return an ENODATA error.

What:		/sys/class/leds/<led>/trigger
Date:		March 2006
KernelVersion:	2.6.17
Contact:	Richard Purdie <rpurdie@rpsys.net>
Description:
		Set the trigger for this LED. A trigger is a kernel based source
		of LED events.

		You can change triggers in a similar manner to the way an IO
		scheduler is chosen. Trigger specific parameters can appear in
		/sys/class/leds/<led> once a given trigger is selected. For
		their documentation see `sysfs-class-led-trigger-*`.

		Writing "none" removes the trigger for this LED.

		Writing "default" sets the trigger to the LED's default trigger
		(which would often be configured in the device tree for the
		hardware).

What:		/sys/class/leds/<led>/trigger_may_offload_to_hw
Date:		September 2026
KernelVersion:	7.4
Contact:	linux-leds@vger.kernel.org
Description:
		Names and states of triggers that may be offloaded to hardware.
		Such triggers are also called "hardware control trigger" in some
		context.

		Only exists when the LED supports trigger offload.

		Reading this file returns a list of triggers that are capable to
		be offloaded. The optional brackets around the trigger name
		indicate the state of the current trigger:

		- `foo_trigger`: the trigger is not selected, or selected but
		  falls back to software blink for some reasons, e.g.,
		  incompatible trigger parameters.
		- `[foo_trigger]`: the trigger is selected and offloaded to
		  hardware.

		The "netdev" trigger also provides a custom attribute to
		indicate its state, see `/sys/class/leds/<led>/offloaded`.

What:		/sys/class/leds/<led>/inverted
Date:		January 2011
KernelVersion:	2.6.38
Contact:	Richard Purdie <rpurdie@rpsys.net>
Description:
		Invert the LED on/off state. This parameter is specific to
		the backlight trigger. It is useful when driving a LED which
		is intended to indicate a device in a standby like state.

What:		/sys/class/leds/<led>/delay_on
Date:		March 2006
KernelVersion:	2.6.17
Contact:	linux-leds@vger.kernel.org
Description:
		This attribute is only present when the LED's trigger is
		set to "timer" or "oneshot".

		For the "timer" trigger, specifies for how many milliseconds
		the LED has to stay on in each cycle of a repeating on/off
		blink. Writing a new value restarts the blink immediately.
		Defaults to 500 ms.

		For the "oneshot" trigger, specifies for how many
		milliseconds the LED has to stay at LED_FULL brightness
		after it has been armed. Defaults to 100 ms.

What:		/sys/class/leds/<led>/delay_off
Date:		March 2006
KernelVersion:	2.6.17
Contact:	linux-leds@vger.kernel.org
Description:
		This attribute is only present when the LED's trigger is
		set to "timer" or "oneshot".

		For the "timer" trigger, specifies for how many milliseconds
		the LED has to stay off in each cycle of a repeating on/off
		blink. Writing a new value restarts the blink immediately.
		Defaults to 500 ms; together with the default delay_on this
		gives a 1 Hz blink.

		For the "oneshot" trigger, specifies for how many
		milliseconds the LED has to stay at LED_OFF brightness
		after it has been armed. Defaults to 100 ms.

What:		/sys/class/leds/<led>/invert
Date:		Jun 2012
KernelVersion:	3.6
Contact:	linux-leds@vger.kernel.org
Description:
		This attribute is only present when the LED's trigger is
		set to "oneshot", "heartbeat" or "activity". Any non-zero
		value written is stored as 1, so reading it back returns
		0 or 1.

		For the "oneshot" trigger, reverses the blink logic. If set
		to 0 (default) blink on for delay_on ms, then blink off for
		delay_off ms, leaving the LED normally off. If set to 1,
		blink off for delay_off ms, then blink on for delay_on ms,
		leaving the LED normally on. Setting this value also
		immediately changes the LED state.

		For the "heartbeat" trigger, inverts the heartbeat pattern.
		If set to 0 (default) the LED stays off most of the time and
		blinks briefly on. If set to 1 the LED stays on most of the
		time and blinks briefly off. Unlike "oneshot", the new value
		only takes effect at the next phase of the pattern.

		For the "activity" trigger, inverts the on/off states of the
		CPU activity blink. If set to 0 (default) the LED is mostly
		off when the system is idle and stays on longer as CPU usage
		grows. If set to 1 the LED is mostly on when idle and stays
		off longer as CPU usage grows. The new value only takes
		effect at the next on/off transition.

		This is unrelated to the /sys/class/leds/<led>/inverted
		attribute, which is specific to the backlight trigger.
