drivers/leds/rgb/leds-lp5860.h
Source file repositories/reference/linux-study-clean/drivers/leds/rgb/leds-lp5860.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/leds/rgb/leds-lp5860.h- Extension
.h- Size
- 7733 bytes
- Lines
- 269
- Domain
- Driver Families
- Bucket
- drivers/leds
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/led-class-multicolor.hlinux/regmap.h
Detected Declarations
struct lp5860_ledstruct lp5860
Annotated Snippet
struct lp5860_led {
struct lp5860 *chip;
struct led_classdev_mc mc_cdev;
u8 brightness;
};
struct lp5860 {
struct device *dev;
struct regmap *regmap;
struct mutex lock;
DECLARE_FLEX_ARRAY(struct lp5860_led, leds);
};
int lp5860_device_init(struct device *dev);
void lp5860_device_remove(struct device *dev);
#endif /* _DRIVERS_LEDS_RGB_LP5860_H */
Annotation
- Immediate include surface: `linux/led-class-multicolor.h`, `linux/regmap.h`.
- Detected declarations: `struct lp5860_led`, `struct lp5860`.
- Atlas domain: Driver Families / drivers/leds.
- Implementation status: source implementation candidate.
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.