drivers/net/ethernet/hisilicon/hns3/hns3_ethtool.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/hisilicon/hns3/hns3_ethtool.h

Extension

.h

Size

661 bytes

Lines

38

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/ethtool.h
• linux/netdevice.h

Detected Declarations

• struct hns3_stats
• struct hns3_sfp_type
• struct hns3_pflag_desc
• struct hns3_ethtool_link_ext_state_mapping
• struct hns3_ring_param

Annotated Snippet

struct hns3_stats {
	char stats_string[ETH_GSTRING_LEN];
	int stats_offset;
};

struct hns3_sfp_type {
	u8 type;
	u8 ext_type;
};

struct hns3_pflag_desc {
	char name[ETH_GSTRING_LEN];
	void (*handler)(struct net_device *netdev, bool enable);
};

struct hns3_ethtool_link_ext_state_mapping {
	u32 status_code;
	enum ethtool_link_ext_state link_ext_state;
	u8 link_ext_substate;
};

struct hns3_ring_param {
	u32 tx_desc_num;
	u32 rx_desc_num;
	u32 rx_buf_len;
};

#endif

Annotation

• Immediate include surface: `linux/ethtool.h`, `linux/netdevice.h`.
• Detected declarations: `struct hns3_stats`, `struct hns3_sfp_type`, `struct hns3_pflag_desc`, `struct hns3_ethtool_link_ext_state_mapping`, `struct hns3_ring_param`.
• 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.