drivers/net/wireless/intel/iwlwifi/mld/led.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/intel/iwlwifi/mld/led.h

Extension

.h

Size

585 bytes

Lines

30

Domain

Driver Families

Bucket

drivers/net

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

• mld.h

Detected Declarations

• function iwl_mld_leds_init
• function iwl_mld_leds_exit

Annotated Snippet

#ifndef __iwl_mld_led_h__
#define __iwl_mld_led_h__

#include "mld.h"

#ifdef CONFIG_IWLWIFI_LEDS
int iwl_mld_leds_init(struct iwl_mld *mld);
void iwl_mld_leds_exit(struct iwl_mld *mld);
void iwl_mld_led_config_fw(struct iwl_mld *mld);
#else
static inline int iwl_mld_leds_init(struct iwl_mld *mld)
{
	return 0;
}

static inline void iwl_mld_leds_exit(struct iwl_mld *mld)
{
}

static inline void iwl_mld_led_config_fw(struct iwl_mld *mld)
{
}
#endif

#endif /* __iwl_mld_led_h__ */

Annotation

• Immediate include surface: `mld.h`.
• Detected declarations: `function iwl_mld_leds_init`, `function iwl_mld_leds_exit`.
• Atlas domain: Driver Families / drivers/net.
• 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.