drivers/accel/habanalabs/include/hw_ip/mmu/mmu_v1_0.h
Source file repositories/reference/linux-study-clean/drivers/accel/habanalabs/include/hw_ip/mmu/mmu_v1_0.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/accel/habanalabs/include/hw_ip/mmu/mmu_v1_0.h- Extension
.h- Size
- 702 bytes
- Lines
- 28
- 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 INCLUDE_MMU_V1_0_H_
#define INCLUDE_MMU_V1_0_H_
#define MMU_V1_0_HOP0_MASK 0x3000000000000ull
#define MMU_V1_0_HOP1_MASK 0x0FF8000000000ull
#define MMU_V1_0_HOP2_MASK 0x0007FC0000000ull
#define MMU_V1_0_HOP3_MASK 0x000003FE00000ull
#define MMU_V1_0_HOP4_MASK 0x00000001FF000ull
#define MMU_V1_0_HOP0_SHIFT 48
#define MMU_V1_0_HOP1_SHIFT 39
#define MMU_V1_0_HOP2_SHIFT 30
#define MMU_V1_0_HOP3_SHIFT 21
#define MMU_V1_0_HOP4_SHIFT 12
#define MMU_HOP0_PA43_12 0x490004
#define MMU_HOP0_PA49_44 0x490008
#define MMU_ASID_BUSY 0x490000
#endif /* INCLUDE_MMU_V1_0_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.