drivers/gpu/drm/amd/display/dc/dio/dcn10/dcn10_dio.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/amd/display/dc/dio/dcn10/dcn10_dio.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/amd/display/dc/dio/dcn10/dcn10_dio.h- Extension
.h- Size
- 833 bytes
- Lines
- 43
- 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
dio.h
Detected Declarations
struct dcn_dio_registersstruct dcn_dio_shiftstruct dcn_dio_maskstruct dcn10_dio
Annotated Snippet
struct dcn_dio_registers {
uint32_t DIO_MEM_PWR_CTRL;
};
struct dcn_dio_shift {
uint8_t I2C_LIGHT_SLEEP_FORCE;
};
struct dcn_dio_mask {
uint32_t I2C_LIGHT_SLEEP_FORCE;
};
struct dcn10_dio {
struct dio base;
const struct dcn_dio_registers *regs;
const struct dcn_dio_shift *shifts;
const struct dcn_dio_mask *masks;
};
void dcn10_dio_construct(
struct dcn10_dio *dio10,
struct dc_context *ctx,
const struct dcn_dio_registers *regs,
const struct dcn_dio_shift *shifts,
const struct dcn_dio_mask *masks);
#endif /* __DCN10_DIO_H__ */
Annotation
- Immediate include surface: `dio.h`.
- Detected declarations: `struct dcn_dio_registers`, `struct dcn_dio_shift`, `struct dcn_dio_mask`, `struct dcn10_dio`.
- 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.