drivers/gpu/drm/amd/display/dc/mmhubbub/dcn42/dcn42_mmhubbub.c
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/amd/display/dc/mmhubbub/dcn42/dcn42_mmhubbub.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/amd/display/dc/mmhubbub/dcn42/dcn42_mmhubbub.c- Extension
.c- Size
- 831 bytes
- Lines
- 26
- 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
dcn35/dcn35_mmhubbub.hdcn42_mmhubbub.hreg_helper.h
Detected Declarations
function dcn42_mmhubbub_set_fgcg
Annotated Snippet
// SPDX-License-Identifier: MIT
//
// Copyright 2026 Advanced Micro Devices, Inc.
#include "dcn35/dcn35_mmhubbub.h"
#include "dcn42_mmhubbub.h"
#include "reg_helper.h"
#define REG(reg) \
((const struct dcn35_mmhubbub_registers *)(mcif_wb30->mcif_wb_regs)) \
->reg
#define CTX mcif_wb30->base.ctx
#undef FN
#define FN(reg_name, field_name) \
((const struct dcn35_mmhubbub_shift *)(mcif_wb30->mcif_wb_shift)) \
->field_name, \
((const struct dcn35_mmhubbub_mask *)(mcif_wb30->mcif_wb_mask)) \
->field_name
void dcn42_mmhubbub_set_fgcg(struct dcn30_mmhubbub *mcif_wb30, bool enabled)
{
REG_UPDATE(MMHUBBUB_CLOCK_CNTL, MMHUBBUB_FGCG_REP_DIS, !enabled);
}
Annotation
- Immediate include surface: `dcn35/dcn35_mmhubbub.h`, `dcn42_mmhubbub.h`, `reg_helper.h`.
- Detected declarations: `function dcn42_mmhubbub_set_fgcg`.
- 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.