drivers/accel/habanalabs/include/gaudi/asic_reg/dma_if_e_n_down_ch0_regs.h
Source file repositories/reference/linux-study-clean/drivers/accel/habanalabs/include/gaudi/asic_reg/dma_if_e_n_down_ch0_regs.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/accel/habanalabs/include/gaudi/asic_reg/dma_if_e_n_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_N_DOWN_CH0_REGS_H_
#define ASIC_REG_DMA_IF_E_N_DOWN_CH0_REGS_H_
/*
*****************************************
* DMA_IF_E_N_DOWN_CH0 (Prototype: RTR_CTRL)
*****************************************
*/
#define mmDMA_IF_E_N_DOWN_CH0_PERM_SEL 0x4E1108
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_0 0x4E1114
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_1 0x4E1118
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_2 0x4E111C
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_3 0x4E1120
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_4 0x4E1124
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_5 0x4E1128
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_6 0x4E112C
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_7 0x4E1130
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_8 0x4E1134
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_9 0x4E1138
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_10 0x4E113C
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_11 0x4E1140
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_12 0x4E1144
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_13 0x4E1148
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_14 0x4E114C
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_15 0x4E1150
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_16 0x4E1154
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_17 0x4E1158
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_18 0x4E115C
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_19 0x4E1160
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_20 0x4E1164
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_21 0x4E1168
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_22 0x4E116C
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_23 0x4E1170
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_24 0x4E1174
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_25 0x4E1178
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_26 0x4E117C
#define mmDMA_IF_E_N_DOWN_CH0_HBM_POLY_H3_27 0x4E1180
#define mmDMA_IF_E_N_DOWN_CH0_SRAM_POLY_H3_0 0x4E1184
#define mmDMA_IF_E_N_DOWN_CH0_SRAM_POLY_H3_1 0x4E1188
#define mmDMA_IF_E_N_DOWN_CH0_SRAM_POLY_H3_2 0x4E118C
#define mmDMA_IF_E_N_DOWN_CH0_SRAM_POLY_H3_3 0x4E1190
#define mmDMA_IF_E_N_DOWN_CH0_SRAM_POLY_H3_4 0x4E1194
#define mmDMA_IF_E_N_DOWN_CH0_SRAM_POLY_H3_5 0x4E1198
#define mmDMA_IF_E_N_DOWN_CH0_SRAM_POLY_H3_6 0x4E119C
#define mmDMA_IF_E_N_DOWN_CH0_SRAM_POLY_H3_7 0x4E11A0
#define mmDMA_IF_E_N_DOWN_CH0_SRAM_POLY_H3_8 0x4E11A4
#define mmDMA_IF_E_N_DOWN_CH0_SRAM_POLY_H3_9 0x4E11A8
#define mmDMA_IF_E_N_DOWN_CH0_SRAM_POLY_H3_10 0x4E11AC
#define mmDMA_IF_E_N_DOWN_CH0_SRAM_POLY_H3_11 0x4E11B0
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.