drivers/gpu/drm/mxsfb/lcdif_drv.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/mxsfb/lcdif_drv.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/mxsfb/lcdif_drv.h- Extension
.h- Size
- 855 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
drm/drm_bridge.hdrm/drm_crtc.hdrm/drm_device.hdrm/drm_plane.h
Detected Declarations
struct clkstruct lcdif_drm_privatefunction to_lcdif_drm_private
Annotated Snippet
struct lcdif_drm_private {
void __iomem *base; /* registers */
struct clk *clk;
struct clk *clk_axi;
struct clk *clk_disp_axi;
unsigned int irq;
struct drm_device *drm;
struct {
struct drm_plane primary;
/* i.MXRT does support overlay planes, add them here. */
} planes;
struct drm_crtc crtc;
};
static inline struct lcdif_drm_private *
to_lcdif_drm_private(struct drm_device *drm)
{
return drm->dev_private;
}
int lcdif_kms_init(struct lcdif_drm_private *lcdif);
#endif /* __LCDIF_DRV_H__ */
Annotation
- Immediate include surface: `drm/drm_bridge.h`, `drm/drm_crtc.h`, `drm/drm_device.h`, `drm/drm_plane.h`.
- Detected declarations: `struct clk`, `struct lcdif_drm_private`, `function to_lcdif_drm_private`.
- 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.