drivers/gpu/drm/amd/display/dc/dpp/dcn35/dcn35_dpp.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/amd/display/dc/dpp/dcn35/dcn35_dpp.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/amd/display/dc/dpp/dcn35/dcn35_dpp.h- Extension
.h- Size
- 2345 bytes
- Lines
- 68
- 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
dcn32/dcn32_dpp.h
Detected Declarations
struct dcn35_dpp_shiftstruct dcn35_dpp_mask
Annotated Snippet
struct dcn35_dpp_shift {
DPP_REG_FIELD_LIST_DCN35(uint8_t);
};
struct dcn35_dpp_mask {
DPP_REG_FIELD_LIST_DCN35(uint32_t);
};
void dpp35_dppclk_control(
struct dpp *dpp_base,
bool dppclk_div,
bool enable);
bool dpp35_construct(struct dcn3_dpp *dpp3, struct dc_context *ctx,
uint32_t inst, const struct dcn3_dpp_registers *tf_regs,
const struct dcn35_dpp_shift *tf_shift,
const struct dcn35_dpp_mask *tf_mask);
void dpp35_set_fgcg(struct dcn3_dpp *dpp, bool enable);
void dpp35_program_bias_and_scale_fcnv(struct dpp *dpp_base,
struct dc_bias_and_scale *bias_and_scale);
#endif // __DCN35_DPP_H
Annotation
- Immediate include surface: `dcn32/dcn32_dpp.h`.
- Detected declarations: `struct dcn35_dpp_shift`, `struct dcn35_dpp_mask`.
- 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.