drivers/accel/habanalabs/include/gaudi/asic_reg/dma_if_e_s_down_ch0_regs.h
Source file repositories/reference/linux-study-clean/drivers/accel/habanalabs/include/gaudi/asic_reg/dma_if_e_s_down_ch0_regs.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/accel/habanalabs/include/gaudi/asic_reg/dma_if_e_s_down_ch0_regs.h- Extension
.h- Size
- 35070 bytes
- Lines
- 897
- 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.
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 ASIC_REG_DMA_IF_E_S_DOWN_CH0_REGS_H_
#define ASIC_REG_DMA_IF_E_S_DOWN_CH0_REGS_H_
/*
*****************************************
* DMA_IF_E_S_DOWN_CH0 (Prototype: RTR_CTRL)
*****************************************
*/
#define mmDMA_IF_E_S_DOWN_CH0_PERM_SEL 0x4A1108
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_0 0x4A1114
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_1 0x4A1118
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_2 0x4A111C
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_3 0x4A1120
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_4 0x4A1124
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_5 0x4A1128
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_6 0x4A112C
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_7 0x4A1130
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_8 0x4A1134
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_9 0x4A1138
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_10 0x4A113C
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_11 0x4A1140
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_12 0x4A1144
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_13 0x4A1148
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_14 0x4A114C
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_15 0x4A1150
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_16 0x4A1154
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_17 0x4A1158
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_18 0x4A115C
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_19 0x4A1160
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_20 0x4A1164
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_21 0x4A1168
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_22 0x4A116C
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_23 0x4A1170
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_24 0x4A1174
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_25 0x4A1178
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_26 0x4A117C
#define mmDMA_IF_E_S_DOWN_CH0_HBM_POLY_H3_27 0x4A1180
#define mmDMA_IF_E_S_DOWN_CH0_SRAM_POLY_H3_0 0x4A1184
#define mmDMA_IF_E_S_DOWN_CH0_SRAM_POLY_H3_1 0x4A1188
#define mmDMA_IF_E_S_DOWN_CH0_SRAM_POLY_H3_2 0x4A118C
#define mmDMA_IF_E_S_DOWN_CH0_SRAM_POLY_H3_3 0x4A1190
#define mmDMA_IF_E_S_DOWN_CH0_SRAM_POLY_H3_4 0x4A1194
#define mmDMA_IF_E_S_DOWN_CH0_SRAM_POLY_H3_5 0x4A1198
#define mmDMA_IF_E_S_DOWN_CH0_SRAM_POLY_H3_6 0x4A119C
#define mmDMA_IF_E_S_DOWN_CH0_SRAM_POLY_H3_7 0x4A11A0
#define mmDMA_IF_E_S_DOWN_CH0_SRAM_POLY_H3_8 0x4A11A4
#define mmDMA_IF_E_S_DOWN_CH0_SRAM_POLY_H3_9 0x4A11A8
#define mmDMA_IF_E_S_DOWN_CH0_SRAM_POLY_H3_10 0x4A11AC
#define mmDMA_IF_E_S_DOWN_CH0_SRAM_POLY_H3_11 0x4A11B0
Annotation
- Atlas domain: Driver Families / drivers/accel.
- 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.