drivers/accel/habanalabs/include/goya/asic_reg/cpu_if_regs.h
Source file repositories/reference/linux-study-clean/drivers/accel/habanalabs/include/goya/asic_reg/cpu_if_regs.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/accel/habanalabs/include/goya/asic_reg/cpu_if_regs.h- Extension
.h- Size
- 1520 bytes
- Lines
- 49
- 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_CPU_IF_REGS_H_
#define ASIC_REG_CPU_IF_REGS_H_
/*
*****************************************
* CPU_IF (Prototype: CPU_IF)
*****************************************
*/
#define mmCPU_IF_PF_PQ_PI 0x442100
#define mmCPU_IF_ARUSER_OVR 0x442104
#define mmCPU_IF_ARUSER_OVR_EN 0x442108
#define mmCPU_IF_AWUSER_OVR 0x44210C
#define mmCPU_IF_AWUSER_OVR_EN 0x442110
#define mmCPU_IF_AXCACHE_OVR 0x442114
#define mmCPU_IF_LOCK_OVR 0x442118
#define mmCPU_IF_PROT_OVR 0x44211C
#define mmCPU_IF_MAX_OUTSTANDING 0x442120
#define mmCPU_IF_EARLY_BRESP_EN 0x442124
#define mmCPU_IF_FORCE_RSP_OK 0x442128
#define mmCPU_IF_CPU_MSB_ADDR 0x44212C
#define mmCPU_IF_AXI_SPLIT_INTR 0x442130
#endif /* ASIC_REG_CPU_IF_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.