drivers/net/ethernet/aquantia/atlantic/aq_drvinfo.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/aquantia/atlantic/aq_drvinfo.c

Extension

.c

Size

3228 bytes

Lines

149

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/init.h
• linux/kobject.h
• linux/module.h
• linux/stat.h
• linux/string.h
• linux/hwmon.h
• linux/uaccess.h
• aq_drvinfo.h
• aq_nic.h

Detected Declarations

• function aq_hwmon_read
• function aq_hwmon_read_string
• function aq_hwmon_is_visible
• function aq_drvinfo_init
• function aq_drvinfo_init

Annotated Snippet

int aq_drvinfo_init(struct net_device *ndev) { return 0; }
#endif

Annotation

• Immediate include surface: `linux/init.h`, `linux/kobject.h`, `linux/module.h`, `linux/stat.h`, `linux/string.h`, `linux/hwmon.h`, `linux/uaccess.h`, `aq_drvinfo.h`.
• Detected declarations: `function aq_hwmon_read`, `function aq_hwmon_read_string`, `function aq_hwmon_is_visible`, `function aq_drvinfo_init`, `function aq_drvinfo_init`.
• 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.