drivers/gpu/drm/i915/display/intel_colorop.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/i915/display/intel_colorop.h

Extension

.h

Size

486 bytes

Lines

19

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 drm_colorop
• struct intel_colorop
• enum intel_color_block

Annotated Snippet

#ifndef __INTEL_COLOROP_H__
#define __INTEL_COLOROP_H__

enum intel_color_block;
struct drm_colorop;
struct intel_colorop;

struct intel_colorop *to_intel_colorop(struct drm_colorop *colorop);
struct intel_colorop *intel_colorop_alloc(void);
struct intel_colorop *intel_colorop_create(enum intel_color_block id);
void intel_colorop_destroy(struct drm_colorop *colorop);

#endif /* __INTEL_COLOROP_H__ */

Annotation

• Detected declarations: `struct drm_colorop`, `struct intel_colorop`, `enum intel_color_block`.
• 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.