include/linux/leds-expresswire.h

File Facts

System

Linux kernel

Corpus path

include/linux/leds-expresswire.h

Extension

.h

Size

959 bytes

Lines

36

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• struct gpio_desc
• struct expresswire_timing
• struct expresswire_common_props

Annotated Snippet

struct expresswire_timing {
	unsigned long poweroff_us;
	unsigned long detect_delay_us;
	unsigned long detect_us;
	unsigned long data_start_us;
	unsigned long end_of_data_low_us;
	unsigned long end_of_data_high_us;
	unsigned long short_bitset_us;
	unsigned long long_bitset_us;
};

struct expresswire_common_props {
	struct gpio_desc *ctrl_gpio;
	struct expresswire_timing timing;
};

void expresswire_power_off(struct expresswire_common_props *props);
void expresswire_enable(struct expresswire_common_props *props);
void expresswire_write_u8(struct expresswire_common_props *props, u8 val);

#endif /* _LEDS_EXPRESSWIRE_H */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct gpio_desc`, `struct expresswire_timing`, `struct expresswire_common_props`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.