drivers/net/phy/aquantia/aquantia_hwmon.c

File Facts

System

Linux kernel

Corpus path

drivers/net/phy/aquantia/aquantia_hwmon.c

Extension

.c

Size

5106 bytes

Lines

217

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
• linux/device.h
• linux/ctype.h
• linux/hwmon.h
• aquantia.h

Detected Declarations

• function aqr_hwmon_is_visible
• function aqr_hwmon_get
• function aqr_hwmon_set
• function aqr_hwmon_test_bit
• function aqr_hwmon_status1
• function aqr_hwmon_read
• function aqr_hwmon_write
• function aqr_hwmon_probe

Annotated Snippet

if (isalnum(hwmon_name[i])) {
			if (i != j)
				hwmon_name[j] = hwmon_name[i];
			j++;
		}
	}
	hwmon_name[j] = '\0';

	hwmon_dev = devm_hwmon_device_register_with_info(dev, hwmon_name,
					phydev, &aqr_hwmon_chip_info, NULL);

	return PTR_ERR_OR_ZERO(hwmon_dev);
}

#endif

Annotation

• Immediate include surface: `linux/phy.h`, `linux/device.h`, `linux/ctype.h`, `linux/hwmon.h`, `aquantia.h`.
• Detected declarations: `function aqr_hwmon_is_visible`, `function aqr_hwmon_get`, `function aqr_hwmon_set`, `function aqr_hwmon_test_bit`, `function aqr_hwmon_status1`, `function aqr_hwmon_read`, `function aqr_hwmon_write`, `function aqr_hwmon_probe`.
• 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.