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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

703 bytes

Lines

26

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

Detected Declarations

• struct drm_device
• struct intel_rom

Annotated Snippet

#ifndef __INTEL_ROM_H__
#define __INTEL_ROM_H__

#include <linux/types.h>

struct drm_device;
struct intel_rom;

struct intel_rom *intel_rom_spi(struct drm_device *drm);
struct intel_rom *intel_rom_pci(struct drm_device *drm);

u32 intel_rom_read32(struct intel_rom *rom, loff_t offset);
u16 intel_rom_read16(struct intel_rom *rom, loff_t offset);
void intel_rom_read_block(struct intel_rom *rom, void *data,
			  loff_t offset, size_t size);
loff_t intel_rom_find(struct intel_rom *rom, u32 needle);
size_t intel_rom_size(struct intel_rom *rom);
void intel_rom_free(struct intel_rom *rom);

#endif /* __INTEL_ROM_H__ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct drm_device`, `struct intel_rom`.
• 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.