drivers/gpu/drm/i915/display/intel_display_utils.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/i915/display/intel_display_utils.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/i915/display/intel_display_utils.h- Extension
.h- Size
- 663 bytes
- Lines
- 28
- 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
linux/bug.hlinux/types.h
Detected Declarations
struct intel_display
Annotated Snippet
#ifndef __INTEL_DISPLAY_UTILS__
#define __INTEL_DISPLAY_UTILS__
#include <linux/bug.h>
#include <linux/types.h>
struct intel_display;
#define MISSING_CASE(x) WARN(1, "Missing case (%s == %ld)\n", \
__stringify(x), (long)(x))
#define fetch_and_zero(ptr) ({ \
typeof(*ptr) __T = *(ptr); \
*(ptr) = (typeof(*ptr))0; \
__T; \
})
#define KHz(x) (1000 * (x))
#define MHz(x) KHz(1000 * (x))
bool intel_display_run_as_guest(struct intel_display *display);
bool intel_display_vtd_active(struct intel_display *display);
#endif /* __INTEL_DISPLAY_UTILS__ */
Annotation
- Immediate include surface: `linux/bug.h`, `linux/types.h`.
- Detected declarations: `struct intel_display`.
- 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.