drivers/leds/trigger/ledtrig-backlight.c
Source file repositories/reference/linux-study-clean/drivers/leds/trigger/ledtrig-backlight.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/leds/trigger/ledtrig-backlight.c- Extension
.c- Size
- 3224 bytes
- Lines
- 141
- Domain
- Driver Families
- Bucket
- drivers/leds
- Inferred role
- Driver Families: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/kernel.hlinux/slab.hlinux/init.hlinux/leds.h../leds.h
Detected Declarations
struct bl_trig_notifierfunction ledtrig_backlight_notify_blankfunction ledtrig_backlight_blankfunction bl_trig_invert_showfunction bl_trig_invert_storefunction bl_trig_activatefunction bl_trig_deactivateexport ledtrig_backlight_blank
Annotated Snippet
struct bl_trig_notifier {
struct led_classdev *led;
int brightness;
int old_status;
unsigned invert;
struct list_head entry;
};
static DEFINE_MUTEX(ledtrig_backlight_list_mutex);
static LIST_HEAD(ledtrig_backlight_list);
static void ledtrig_backlight_notify_blank(struct bl_trig_notifier *n, int new_status)
{
struct led_classdev *led = n->led;
if (new_status == n->old_status)
return;
if ((n->old_status == UNBLANK) ^ n->invert) {
n->brightness = led->brightness;
led_set_brightness_nosleep(led, LED_OFF);
} else {
led_set_brightness_nosleep(led, n->brightness);
}
n->old_status = new_status;
}
void ledtrig_backlight_blank(bool blank)
{
struct bl_trig_notifier *n;
int new_status = blank ? BLANK : UNBLANK;
guard(mutex)(&ledtrig_backlight_list_mutex);
list_for_each_entry(n, &ledtrig_backlight_list, entry)
ledtrig_backlight_notify_blank(n, new_status);
}
EXPORT_SYMBOL(ledtrig_backlight_blank);
static ssize_t bl_trig_invert_show(struct device *dev,
struct device_attribute *attr, char *buf)
{
struct bl_trig_notifier *n = led_trigger_get_drvdata(dev);
return sprintf(buf, "%u\n", n->invert);
}
static ssize_t bl_trig_invert_store(struct device *dev,
struct device_attribute *attr, const char *buf, size_t num)
{
struct led_classdev *led = led_trigger_get_led(dev);
struct bl_trig_notifier *n = led_trigger_get_drvdata(dev);
unsigned long invert;
int ret;
ret = kstrtoul(buf, 10, &invert);
if (ret < 0)
return ret;
if (invert > 1)
return -EINVAL;
n->invert = invert;
/* After inverting, we need to update the LED. */
if ((n->old_status == BLANK) ^ n->invert)
led_set_brightness_nosleep(led, LED_OFF);
else
led_set_brightness_nosleep(led, n->brightness);
return num;
}
static DEVICE_ATTR(inverted, 0644, bl_trig_invert_show, bl_trig_invert_store);
static struct attribute *bl_trig_attrs[] = {
&dev_attr_inverted.attr,
NULL,
};
ATTRIBUTE_GROUPS(bl_trig);
static int bl_trig_activate(struct led_classdev *led)
{
struct bl_trig_notifier *n;
n = kzalloc_obj(struct bl_trig_notifier);
if (!n)
return -ENOMEM;
led_set_trigger_data(led, n);
Annotation
- Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/slab.h`, `linux/init.h`, `linux/leds.h`, `../leds.h`.
- Detected declarations: `struct bl_trig_notifier`, `function ledtrig_backlight_notify_blank`, `function ledtrig_backlight_blank`, `function bl_trig_invert_show`, `function bl_trig_invert_store`, `function bl_trig_activate`, `function bl_trig_deactivate`, `export ledtrig_backlight_blank`.
- Atlas domain: Driver Families / drivers/leds.
- Implementation status: integration 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.