drivers/gpu/drm/imagination/pvr_power.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/imagination/pvr_power.h

Extension

.h

Size

1743 bytes

Lines

60

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

• pvr_device.h
• linux/mutex.h
• linux/pm_runtime.h

Detected Declarations

• struct pvr_power_sequence_ops
• function pvr_power_get
• function pvr_power_put

Annotated Snippet

struct pvr_power_sequence_ops {
	int (*init)(struct pvr_device *pvr_dev);
	int (*power_on)(struct pvr_device *pvr_dev);
	int (*power_off)(struct pvr_device *pvr_dev);
};

extern const struct pvr_power_sequence_ops pvr_power_sequence_ops_manual;
extern const struct pvr_power_sequence_ops pvr_power_sequence_ops_pwrseq;

#endif /* PVR_POWER_H */

Annotation

• Immediate include surface: `pvr_device.h`, `linux/mutex.h`, `linux/pm_runtime.h`.
• Detected declarations: `struct pvr_power_sequence_ops`, `function pvr_power_get`, `function pvr_power_put`.
• 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.