drivers/net/ethernet/renesas/rtsn.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/renesas/rtsn.h

Extension

.h

Size

11239 bytes

Lines

465

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• struct rtsn_desc
• struct rtsn_ts_desc
• struct rtsn_ext_desc
• struct rtsn_ext_ts_desc
• enum rtsn_reg
• enum rtsn_mode
• enum RX_DS_CC_BIT
• enum TX_FS_TAGL_BIT
• enum DIE_DT
• enum EXT_INFO_DS_BIT

Annotated Snippet

struct rtsn_desc {
	__le16 info_ds;
	__u8 info;
	u8 die_dt;
	__le32 dptr;
} __packed;

struct rtsn_ts_desc {
	__le16 info_ds;
	__u8 info;
	u8 die_dt;
	__le32 dptr;
	__le32 ts_nsec;
	__le32 ts_sec;
} __packed;

struct rtsn_ext_desc {
	__le16 info_ds;
	__u8 info;
	u8 die_dt;
	__le32 dptr;
	__le64 info1;
} __packed;

struct rtsn_ext_ts_desc {
	__le16 info_ds;
	__u8 info;
	u8 die_dt;
	__le32 dptr;
	__le64 info1;
	__le32 ts_nsec;
	__le32 ts_sec;
} __packed;

enum EXT_INFO_DS_BIT {
	TXC = 0x4000,
};

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct rtsn_desc`, `struct rtsn_ts_desc`, `struct rtsn_ext_desc`, `struct rtsn_ext_ts_desc`, `enum rtsn_reg`, `enum rtsn_mode`, `enum RX_DS_CC_BIT`, `enum TX_FS_TAGL_BIT`, `enum DIE_DT`, `enum EXT_INFO_DS_BIT`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: source implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.