drivers/net/phy/aquantia/aquantia_leds.c

File Facts

System

Linux kernel

Corpus path

drivers/net/phy/aquantia/aquantia_leds.c

Extension

.c

Size

4287 bytes

Lines

161

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

• linux/phy.h
• aquantia.h

Detected Declarations

• function aqr_phy_led_brightness_set
• function aqr_phy_led_hw_is_supported
• function aqr_phy_led_hw_control_get
• function aqr_phy_led_hw_control_set
• function aqr_phy_led_active_low_set
• function aqr_phy_led_polarity_set
• function for_each_set_bit

Annotated Snippet

switch (mode) {
		case PHY_LED_ACTIVE_LOW:
			force_active_low = true;
			break;
		case PHY_LED_ACTIVE_HIGH:
			force_active_high = true;
			break;
		default:
			return -EINVAL;
		}
	}

	/* Save LED driver vdd state to restore on SW reset */
	if (force_active_low)
		priv->leds_active_low |= BIT(index);

	if (force_active_high)
		priv->leds_active_high |= BIT(index);

	if (force_active_high || force_active_low)
		return aqr_phy_led_active_low_set(phydev, index, force_active_low);

	return -EINVAL;
}

Annotation

• Immediate include surface: `linux/phy.h`, `aquantia.h`.
• Detected declarations: `function aqr_phy_led_brightness_set`, `function aqr_phy_led_hw_is_supported`, `function aqr_phy_led_hw_control_get`, `function aqr_phy_led_hw_control_set`, `function aqr_phy_led_active_low_set`, `function aqr_phy_led_polarity_set`, `function for_each_set_bit`.
• 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.