drivers/accel/habanalabs/include/gaudi/gaudi_fw_if.h

File Facts

System

Linux kernel

Corpus path

drivers/accel/habanalabs/include/gaudi/gaudi_fw_if.h

Extension

.h

Size

1231 bytes

Lines

60

Domain

Driver Families

Bucket

drivers/accel

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

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

Detected Declarations

• struct eq_nic_sei_event
• struct gaudi_cold_rst_data
• enum gaudi_nic_axi_error

Annotated Snippet

struct eq_nic_sei_event {
	__u8 axi_error_cause;
	__u8 id;
	__u8 pad[6];
};

struct gaudi_cold_rst_data {
	union {
		struct {
			u32 spsram_init_done : 1;
			u32 reserved : 31;
		};
		__le32 data;
	};
};

#define GAUDI_PLL_FREQ_LOW		200000000 /* 200 MHz */

#endif /* GAUDI_FW_IF_H */

Annotation

• Detected declarations: `struct eq_nic_sei_event`, `struct gaudi_cold_rst_data`, `enum gaudi_nic_axi_error`.
• Atlas domain: Driver Families / drivers/accel.
• 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.