drivers/gpu/drm/i915/i915_timer_util.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/i915/i915_timer_util.h

Extension

.h

Size

538 bytes

Lines

24

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/timer.h
• asm/rwonce.h

Detected Declarations

• function timer_active
• function timer_expired

Annotated Snippet

#ifndef __I915_TIMER_UTIL_H__
#define __I915_TIMER_UTIL_H__

#include <linux/timer.h>
#include <asm/rwonce.h>

void cancel_timer(struct timer_list *t);
void set_timer_ms(struct timer_list *t, unsigned long timeout);

static inline bool timer_active(const struct timer_list *t)
{
	return READ_ONCE(t->expires);
}

static inline bool timer_expired(const struct timer_list *t)
{
	return timer_active(t) && !timer_pending(t);
}

#endif /* __I915_TIMER_UTIL_H__ */

Annotation

• Immediate include surface: `linux/timer.h`, `asm/rwonce.h`.
• Detected declarations: `function timer_active`, `function timer_expired`.
• 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.