drivers/gpu/drm/i915/gem/i915_gem_tiling.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/i915/gem/i915_gem_tiling.h

Extension

.h

Size

566 bytes

Lines

21

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_i915_gem_object
• struct drm_i915_private

Annotated Snippet

#ifndef __I915_GEM_TILING_H__
#define __I915_GEM_TILING_H__

#include <linux/types.h>

struct drm_i915_gem_object;
struct drm_i915_private;

bool i915_gem_object_needs_bit17_swizzle(struct drm_i915_gem_object *obj);
u32 i915_gem_fence_size(struct drm_i915_private *i915, u32 size,
			unsigned int tiling, unsigned int stride);
u32 i915_gem_fence_alignment(struct drm_i915_private *i915, u32 size,
			     unsigned int tiling, unsigned int stride);

#endif /* __I915_GEM_TILING_H__ */

Annotation

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