drivers/gpu/drm/i915/display/intel_display_conversion.c
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/i915/display/intel_display_conversion.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/i915/display/intel_display_conversion.c- Extension
.c- Size
- 622 bytes
- Lines
- 22
- 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/intel/display_member.hintel_display_conversion.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: MIT
/* Copyright © 2024 Intel Corporation */
#include <drm/intel/display_member.h>
#include "intel_display_conversion.h"
struct intel_display *__drm_to_display(struct drm_device *drm)
{
/*
* Note: This relies on both struct drm_i915_private and struct
* xe_device having the struct drm_device and struct intel_display *
* members at the same relative offsets, as defined by struct
* __intel_generic_device.
*
* See also INTEL_DISPLAY_MEMBER_STATIC_ASSERT().
*/
struct __intel_generic_device *d = container_of(drm, struct __intel_generic_device, drm);
return d->display;
}
Annotation
- Immediate include surface: `drm/intel/display_member.h`, `intel_display_conversion.h`.
- 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.