drivers/gpu/drm/amd/ras/rascore/ras_nbio.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/amd/ras/rascore/ras_nbio.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/amd/ras/rascore/ras_nbio.h- Extension
.h- Size
- 1870 bytes
- Lines
- 47
- Domain
- Driver Families
- Bucket
- drivers/gpu
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
ras.h
Detected Declarations
struct ras_core_contextstruct ras_nbio_ip_funcstruct ras_nbio
Annotated Snippet
struct ras_nbio_ip_func {
int (*handle_ras_controller_intr_no_bifring)(struct ras_core_context *ras_core);
int (*handle_ras_err_event_athub_intr_no_bifring)(struct ras_core_context *ras_core);
uint32_t (*get_memory_partition_mode)(struct ras_core_context *ras_core);
};
struct ras_nbio {
uint32_t nbio_ip_version;
const struct ras_nbio_ip_func *ip_func;
const struct ras_nbio_sys_func *sys_func;
};
int ras_nbio_hw_init(struct ras_core_context *ras_core);
int ras_nbio_hw_fini(struct ras_core_context *ras_core);
bool ras_nbio_handle_irq_error(struct ras_core_context *ras_core, void *data);
#endif
Annotation
- Immediate include surface: `ras.h`.
- Detected declarations: `struct ras_core_context`, `struct ras_nbio_ip_func`, `struct ras_nbio`.
- Atlas domain: Driver Families / drivers/gpu.
- 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.