include/linux/dsa/tag_qca.h

File Facts

System

Linux kernel

Corpus path

include/linux/dsa/tag_qca.h

Extension

.h

Size

2586 bytes

Lines

88

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• struct dsa_switch
• struct sk_buff
• struct qca_mgmt_ethhdr
• struct mib_ethhdr
• struct qca_tagger_data
• enum mdio_cmd

Annotated Snippet

struct qca_mgmt_ethhdr {
	__le32 command;		/* command bit 31:0 */
	__le32 seq;		/* seq 63:32 */
	__le32 mdio_data;		/* first 4byte mdio */
	__be16 hdr;		/* qca hdr */
} __packed;

enum mdio_cmd {
	MDIO_WRITE = 0x0,
	MDIO_READ
};

struct mib_ethhdr {
	__le32 data[3];		/* first 3 mib counter */
	__be16 hdr;		/* qca hdr */
} __packed;

struct qca_tagger_data {
	void (*rw_reg_ack_handler)(struct dsa_switch *ds,
				   struct sk_buff *skb);
	void (*mib_autocast_handler)(struct dsa_switch *ds,
				     struct sk_buff *skb);
};

#endif /* __TAG_QCA_H */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct dsa_switch`, `struct sk_buff`, `struct qca_mgmt_ethhdr`, `struct mib_ethhdr`, `struct qca_tagger_data`, `enum mdio_cmd`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.