drivers/net/ethernet/huawei/hinic3/hinic3_lld.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/huawei/hinic3/hinic3_lld.h

Extension

.h

Size

634 bytes

Lines

22

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/auxiliary_bus.h

Detected Declarations

• struct hinic3_event_info

Annotated Snippet

#ifndef _HINIC3_LLD_H_
#define _HINIC3_LLD_H_

#include <linux/auxiliary_bus.h>

struct hinic3_event_info;

#define HINIC3_NIC_DRV_NAME "hinic3"

int hinic3_lld_init(void);
void hinic3_lld_exit(void);
void hinic3_adev_event_register(struct auxiliary_device *adev,
				void (*event_handler)(struct auxiliary_device *adev,
						      struct hinic3_event_info *event));
void hinic3_adev_event_unregister(struct auxiliary_device *adev);
struct hinic3_hwdev *hinic3_adev_get_hwdev(struct auxiliary_device *adev);

#endif

Annotation

• Immediate include surface: `linux/auxiliary_bus.h`.
• Detected declarations: `struct hinic3_event_info`.
• 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.