drivers/gpu/drm/amd/display/dc/mmhubbub/dcn35/dcn35_mmhubbub.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/amd/display/dc/mmhubbub/dcn35/dcn35_mmhubbub.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/amd/display/dc/mmhubbub/dcn35/dcn35_mmhubbub.h- Extension
.h- Size
- 2837 bytes
- Lines
- 76
- 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
mcif_wb.hdcn32/dcn32_mmhubbub.h
Detected Declarations
struct dcn35_mmhubbub_registersstruct dcn35_mmhubbub_maskstruct dcn35_mmhubbub_shift
Annotated Snippet
struct dcn35_mmhubbub_registers {
MCIF_WB_REG_VARIABLE_LIST_DCN3_5;
};
struct dcn35_mmhubbub_mask {
MCIF_WB_REG_FIELD_LIST_DCN3_5(uint32_t);
};
struct dcn35_mmhubbub_shift {
MCIF_WB_REG_FIELD_LIST_DCN3_5(uint8_t);
};
void dcn35_mmhubbub_construct(
struct dcn30_mmhubbub *mcif_wb30, struct dc_context *ctx,
const struct dcn35_mmhubbub_registers *mcif_wb_regs,
const struct dcn35_mmhubbub_shift *mcif_wb_shift,
const struct dcn35_mmhubbub_mask *mcif_wb_mask, int inst);
void dcn35_mmhubbub_set_fgcg(struct dcn30_mmhubbub *mcif_wb30, bool enabled);
#endif // __DCN35_MMHUBBUB_H
Annotation
- Immediate include surface: `mcif_wb.h`, `dcn32/dcn32_mmhubbub.h`.
- Detected declarations: `struct dcn35_mmhubbub_registers`, `struct dcn35_mmhubbub_mask`, `struct dcn35_mmhubbub_shift`.
- 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.