drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.h

Extension

.h

Size

905 bytes

Lines

34

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

• No C-style include directives detected by the generator.

Detected Declarations

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

Annotated Snippet

#ifndef __RVU_NPC_FS_H
#define __RVU_NPC_FS_H

#define IPV6_WORDS	4
#define NPC_BYTESM	GENMASK_ULL(19, 16)
#define NPC_HDR_OFFSET	GENMASK_ULL(15, 8)
#define NPC_KEY_OFFSET	GENMASK_ULL(5, 0)
#define NPC_LDATA_EN	BIT_ULL(7)

void npc_update_entry(struct rvu *rvu, enum key_fields type,
		      struct mcam_entry_mdata *mdata, u64 val_lo,
		      u64 val_hi, u64 mask_lo, u64 mask_hi, u8 intf);

void npc_update_flow(struct rvu *rvu, struct mcam_entry_mdata *mdata,
		     u64 features, struct flow_msg *pkt,
		     struct flow_msg *mask,
		     struct rvu_npc_mcam_rule *output, u8 intf,
		     int blkaddr);

void
npc_populate_mcam_mdata(struct rvu *rvu,
			struct mcam_entry_mdata *mdata,
			struct cn20k_mcam_entry *cn20k_entry,
			struct mcam_entry *entry);

#endif /* RVU_NPC_FS_H */

Annotation

• 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.