drivers/gpu/drm/kmb/kmb_plane.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/kmb/kmb_plane.h

Extension

.h

Size

1880 bytes

Lines

75

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_fourcc.h
• drm/drm_plane.h

Detected Declarations

• struct kmb_plane
• struct layer_status
• struct disp_cfg
• enum layer_id
• enum sub_plane_id

Annotated Snippet

struct kmb_plane {
	struct drm_plane base_plane;
	unsigned char id;
};

struct layer_status {
	bool disable;
	u32 ctrl;
};

struct disp_cfg {
	unsigned int width;
	unsigned int height;
	unsigned int format;
};

struct kmb_plane *kmb_plane_init(struct drm_device *drm);
void kmb_plane_destroy(struct drm_plane *plane);
#endif /* __KMB_PLANE_H__ */

Annotation

• Immediate include surface: `drm/drm_fourcc.h`, `drm/drm_plane.h`.
• Detected declarations: `struct kmb_plane`, `struct layer_status`, `struct disp_cfg`, `enum layer_id`, `enum sub_plane_id`.
• 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.