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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

514 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

• linux/types.h
• drm/intel/mchbar_regs.h
• intel_display_reg_defs.h

Detected Declarations

• struct intel_display

Annotated Snippet

#ifndef __INTEL_MCHBAR_H__
#define __INTEL_MCHBAR_H__

#include <linux/types.h>

#include <drm/intel/mchbar_regs.h>

#include "intel_display_reg_defs.h"

struct intel_display;

u16 intel_mchbar_read16(struct intel_display *display, intel_reg_t reg);
u32 intel_mchbar_read(struct intel_display *display, intel_reg_t reg);
u64 intel_mchbar_read64_2x32(struct intel_display *display, intel_reg_t reg);

#endif /* __INTEL_MCHBAR_H__ */

Annotation

• Immediate include surface: `linux/types.h`, `drm/intel/mchbar_regs.h`, `intel_display_reg_defs.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.