drivers/gpu/drm/sun4i/sun4i_layer.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/sun4i/sun4i_layer.h

Extension

.h

Size

915 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

• No C-style include directives detected by the generator.

Detected Declarations

• struct sunxi_engine
• struct sun4i_layer
• struct sun4i_layer_state
• function plane_to_sun4i_layer
• function state_to_sun4i_layer_state

Annotated Snippet

struct sun4i_layer {
	struct drm_plane	plane;
	struct sun4i_drv	*drv;
	struct sun4i_backend	*backend;
	int			id;
};

struct sun4i_layer_state {
	struct drm_plane_state	state;
	unsigned int		pipe;
	bool			uses_frontend;
};

static inline struct sun4i_layer *
plane_to_sun4i_layer(struct drm_plane *plane)
{
	return container_of(plane, struct sun4i_layer, plane);
}

static inline struct sun4i_layer_state *
state_to_sun4i_layer_state(struct drm_plane_state *state)
{
	return container_of(state, struct sun4i_layer_state, state);
}

struct drm_plane **sun4i_layers_init(struct drm_device *drm,
				     struct sunxi_engine *engine);

#endif /* _SUN4I_LAYER_H_ */

Annotation

• Detected declarations: `struct sunxi_engine`, `struct sun4i_layer`, `struct sun4i_layer_state`, `function plane_to_sun4i_layer`, `function state_to_sun4i_layer_state`.
• 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.