drivers/gpu/drm/i915/display/intel_modeset_lock.c

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/i915/display/intel_modeset_lock.c

Extension

.c

Size

923 bytes

Lines

51

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• drm/drm_modeset_lock.h
• intel_display_types.h
• intel_modeset_lock.h

Detected Declarations

• function _intel_modeset_lock_begin
• function _intel_modeset_lock_loop
• function _intel_modeset_lock_end

Annotated Snippet

if (*ret == 0) {
			*ret = -EDEADLK;
			return;
		}
	}

	drm_modeset_drop_locks(ctx);
	drm_modeset_acquire_fini(ctx);
}

Annotation

• Immediate include surface: `drm/drm_modeset_lock.h`, `intel_display_types.h`, `intel_modeset_lock.h`.
• Detected declarations: `function _intel_modeset_lock_begin`, `function _intel_modeset_lock_loop`, `function _intel_modeset_lock_end`.
• Atlas domain: Driver Families / drivers/gpu.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.