drivers/net/can/spi/mcp251xfd/mcp251xfd-ram.h

File Facts

System

Linux kernel

Corpus path

drivers/net/can/spi/mcp251xfd/mcp251xfd-ram.h

Extension

.h

Size

1059 bytes

Lines

63

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

Detected Declarations

• struct can_ram_obj_config
• struct can_ram_config
• struct can_ram_layout
• enum can_ram_mode

Annotated Snippet

struct can_ram_obj_config {
	u8 size[__CAN_RAM_MODE_MAX];

	u8 def[__CAN_RAM_MODE_MAX];
	u8 min;
	u8 max;

	u8 fifo_num;
	u8 fifo_depth_min;
	u8 fifo_depth_coalesce_min;
};

struct can_ram_config {
	const struct can_ram_obj_config rx;
	const struct can_ram_obj_config tx;

	u16 size;
	u8 fifo_depth;
};

struct can_ram_layout {
	u8 default_rx;
	u8 default_tx;

	u8 max_rx;
	u8 max_tx;

	u8 cur_rx;
	u8 cur_tx;

	u8 rx_coalesce;
	u8 tx_coalesce;
};

void can_ram_get_layout(struct can_ram_layout *layout,
			const struct can_ram_config *config,
			const struct ethtool_ringparam *ring,
			const struct ethtool_coalesce *ec,
			const bool fd_mode);

#endif

Annotation

• Immediate include surface: `linux/ethtool.h`.
• Detected declarations: `struct can_ram_obj_config`, `struct can_ram_config`, `struct can_ram_layout`, `enum can_ram_mode`.
• 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.