drivers/net/ethernet/apm/xgene/xgene_enet_ring2.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/apm/xgene/xgene_enet_ring2.h

Extension

.h

Size

926 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

• xgene_enet_main.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef __XGENE_ENET_RING2_H__
#define __XGENE_ENET_RING2_H__

#include "xgene_enet_main.h"

#define X2_NUM_RING_CONFIG	6

#define INTR_MBOX_SIZE		1024
#define CSR_VMID0_INTR_MBOX	0x0270
#define INTR_CLEAR		BIT(23)

#define X2_MSG_AM_POS		10
#define X2_QBASE_AM_POS		11
#define X2_INTLINE_POS		24
#define X2_INTLINE_LEN		5
#define X2_CFGCRID_POS		29
#define X2_CFGCRID_LEN		3
#define X2_SELTHRSH_POS		7
#define X2_SELTHRSH_LEN		3
#define X2_RINGTYPE_POS		23
#define X2_RINGTYPE_LEN		2
#define X2_DEQINTEN_POS		29
#define X2_RECOMTIMEOUT_POS	0
#define X2_RECOMTIMEOUT_LEN	7
#define X2_NUMMSGSINQ_POS	0
#define X2_NUMMSGSINQ_LEN	17

extern struct xgene_ring_ops xgene_ring2_ops;

#endif /* __XGENE_ENET_RING2_H__ */

Annotation

• Immediate include surface: `xgene_enet_main.h`.
• 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.