drivers/gpu/drm/msm/disp/dpu1/dpu_writeback.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/msm/disp/dpu1/dpu_writeback.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/msm/disp/dpu1/dpu_writeback.h- Extension
.h- Size
- 806 bytes
- Lines
- 33
- 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
drm/drm_crtc.hdrm/drm_file.hdrm/drm_probe_helper.hdrm/drm_writeback.hmsm_drv.hdpu_kms.hdpu_encoder_phys.h
Detected Declarations
struct dpu_wb_connector
Annotated Snippet
struct dpu_wb_connector {
struct drm_writeback_connector base;
struct drm_encoder *wb_enc;
u32 maxlinewidth;
};
static inline struct dpu_wb_connector *to_dpu_wb_conn(struct drm_writeback_connector *conn)
{
return container_of(conn, struct dpu_wb_connector, base);
}
int dpu_writeback_init(struct drm_device *dev, struct drm_encoder *enc,
const u32 *format_list, u32 num_formats, u32 maxlinewidth);
#endif /*_DPU_WRITEBACK_H */
Annotation
- Immediate include surface: `drm/drm_crtc.h`, `drm/drm_file.h`, `drm/drm_probe_helper.h`, `drm/drm_writeback.h`, `msm_drv.h`, `dpu_kms.h`, `dpu_encoder_phys.h`.
- Detected declarations: `struct dpu_wb_connector`.
- 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.