drivers/gpu/host1x/context.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/host1x/context.h

Extension

.h

Size

762 bytes

Lines

38

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/mutex.h
• linux/refcount.h

Detected Declarations

• struct host1x
• struct host1x_memory_context
• struct host1x_memory_context_list
• function host1x_memory_context_list_init
• function host1x_memory_context_list_free

Annotated Snippet

struct host1x_memory_context_list {
	struct mutex lock;
	struct host1x_memory_context *devs;
	unsigned int len;
};

#ifdef CONFIG_IOMMU_API
int host1x_memory_context_list_init(struct host1x *host1x);
void host1x_memory_context_list_free(struct host1x_memory_context_list *cdl);
#else
static inline int host1x_memory_context_list_init(struct host1x *host1x)
{
	return 0;
}

static inline void host1x_memory_context_list_free(struct host1x_memory_context_list *cdl)
{
}
#endif

#endif

Annotation

• Immediate include surface: `linux/mutex.h`, `linux/refcount.h`.
• Detected declarations: `struct host1x`, `struct host1x_memory_context`, `struct host1x_memory_context_list`, `function host1x_memory_context_list_init`, `function host1x_memory_context_list_free`.
• 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.