drivers/accel/habanalabs/include/goya/asic_reg/mmu_regs.h
Source file repositories/reference/linux-study-clean/drivers/accel/habanalabs/include/goya/asic_reg/mmu_regs.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/accel/habanalabs/include/goya/asic_reg/mmu_regs.h- Extension
.h- Size
- 1663 bytes
- Lines
- 53
- 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_MMU_REGS_H_
#define ASIC_REG_MMU_REGS_H_
/*
*****************************************
* MMU (Prototype: MMU)
*****************************************
*/
#define mmMMU_INPUT_FIFO_THRESHOLD 0x480000
#define mmMMU_MMU_ENABLE 0x48000C
#define mmMMU_FORCE_ORDERING 0x480010
#define mmMMU_FEATURE_ENABLE 0x480014
#define mmMMU_VA_ORDERING_MASK_31_7 0x480018
#define mmMMU_VA_ORDERING_MASK_49_32 0x48001C
#define mmMMU_LOG2_DDR_SIZE 0x480020
#define mmMMU_SCRAMBLER 0x480024
#define mmMMU_MEM_INIT_BUSY 0x480028
#define mmMMU_SPI_MASK 0x48002C
#define mmMMU_SPI_CAUSE 0x480030
#define mmMMU_PAGE_ERROR_CAPTURE 0x480034
#define mmMMU_PAGE_ERROR_CAPTURE_VA 0x480038
#define mmMMU_ACCESS_ERROR_CAPTURE 0x48003C
#define mmMMU_ACCESS_ERROR_CAPTURE_VA 0x480040
#endif /* ASIC_REG_MMU_REGS_H_ */
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.