drivers/gpu/host1x/intr.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/host1x/intr.h

Extension

.h

Size

920 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

• No C-style include directives detected by the generator.

Detected Declarations

• struct host1x
• struct host1x_syncpt_fence
• struct host1x_intr_irq_data

Annotated Snippet

struct host1x_intr_irq_data {
	struct host1x *host;
	u32 offset;
};

/* Initialize host1x sync point interrupt */
int host1x_intr_init(struct host1x *host);

/* Deinitialize host1x sync point interrupt */
void host1x_intr_deinit(struct host1x *host);

/* Enable host1x sync point interrupt */
void host1x_intr_start(struct host1x *host);

/* Disable host1x sync point interrupt */
void host1x_intr_stop(struct host1x *host);

void host1x_intr_handle_interrupt(struct host1x *host, unsigned int id);

void host1x_intr_add_fence_locked(struct host1x *host, struct host1x_syncpt_fence *fence);

bool host1x_intr_remove_fence(struct host1x *host, struct host1x_syncpt_fence *fence);

#endif

Annotation

• Detected declarations: `struct host1x`, `struct host1x_syncpt_fence`, `struct host1x_intr_irq_data`.
• 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.