Documentation/devicetree/bindings/leds/leds-consumer.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/leds/leds-consumer.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/leds/leds-consumer.yaml- Extension
.yaml- Size
- 1654 bytes
- Lines
- 68
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
dt-bindings/gpio/gpio.hdt-bindings/leds/common.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/leds/leds-consumer.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Common leds consumer
maintainers:
- Aleksandrs Vinarskis <alex@vinarskis.com>
description:
Some LED defined in DT are required by other DT consumers, for example
v4l2 subnode may require privacy or flash LED. Unlike trigger-source
approach which is typically used as 'soft' binding, referencing LED
devices by phandle makes things simpler when 'hard' binding is desired.
Document LED properties that its consumers may define.
select: true
properties:
leds:
oneOf:
- type: object
- $ref: /schemas/types.yaml#/definitions/phandle-array
description:
A list of LED device(s) required by a particular consumer.
items:
maxItems: 1
led-names:
description:
A list of device name(s). Used to map LED devices to their respective
functions, when consumer requires more than one LED.
additionalProperties: true
examples:
- |
#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/leds/common.h>
leds {
compatible = "gpio-leds";
privacy_led: privacy-led {
color = <LED_COLOR_ID_RED>;
default-state = "off";
function = LED_FUNCTION_INDICATOR;
gpios = <&tlmm 110 GPIO_ACTIVE_HIGH>;
};
};
i2c {
#address-cells = <1>;
#size-cells = <0>;
v4l2_node: camera@36 {
reg = <0x36>;
leds = <&privacy_led>;
led-names = "privacy";
};
};
...
Annotation
- Immediate include surface: `dt-bindings/gpio/gpio.h`, `dt-bindings/leds/common.h`.
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.