drivers/gpu/drm/msm/disp/mdp5/mdp5_mixer.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/msm/disp/mdp5/mdp5_mixer.h

Extension

.h

Size

974 bytes

Lines

37

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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 mdp5_hw_mixer
• struct mdp5_hw_mixer_state

Annotated Snippet

struct mdp5_hw_mixer {
	int idx;

	const char *name;

	int lm;			/* the LM instance # */
	uint32_t caps;
	int pp;
	int dspp;

	uint32_t flush_mask;      /* used to commit LM registers */
};

/* global atomic state of assignment between CRTCs and Layer Mixers: */
struct mdp5_hw_mixer_state {
	struct drm_crtc *hwmixer_to_crtc[8];
};

struct mdp5_hw_mixer *mdp5_mixer_init(struct drm_device *dev,
				      const struct mdp5_lm_instance *lm);
int mdp5_mixer_assign(struct drm_atomic_commit *s, struct drm_crtc *crtc,
		      uint32_t caps, struct mdp5_hw_mixer **mixer,
		      struct mdp5_hw_mixer **r_mixer);
int mdp5_mixer_release(struct drm_atomic_commit *s,
		       struct mdp5_hw_mixer *mixer);

#endif /* __MDP5_LM_H__ */

Annotation

• Detected declarations: `struct mdp5_hw_mixer`, `struct mdp5_hw_mixer_state`.
• Atlas domain: Driver Families / drivers/gpu.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.