drivers/gpu/drm/etnaviv/etnaviv_perfmon.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/etnaviv/etnaviv_perfmon.h

Extension

.h

Size

844 bytes

Lines

39

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 etnaviv_gpu
• struct drm_etnaviv_pm_domain
• struct drm_etnaviv_pm_signal
• struct etnaviv_perfmon_request

Annotated Snippet

#ifndef __ETNAVIV_PERFMON_H__
#define __ETNAVIV_PERFMON_H__

struct etnaviv_gpu;
struct drm_etnaviv_pm_domain;
struct drm_etnaviv_pm_signal;

struct etnaviv_perfmon_request
{
	u32 flags;
	u8 domain;
	u8 signal;
	u32 sequence;

	/* bo to store a value */
	u32 *bo_vma;
	u32 offset;
};

int etnaviv_pm_query_dom(struct etnaviv_gpu *gpu,
	struct drm_etnaviv_pm_domain *domain);

int etnaviv_pm_query_sig(struct etnaviv_gpu *gpu,
	struct drm_etnaviv_pm_signal *signal);

int etnaviv_pm_req_validate(const struct drm_etnaviv_gem_submit_pmr *r,
	u32 exec_state);

void etnaviv_perfmon_process(struct etnaviv_gpu *gpu,
	const struct etnaviv_perfmon_request *pmr, u32 exec_state);

#endif /* __ETNAVIV_PERFMON_H__ */

Annotation

• Detected declarations: `struct etnaviv_gpu`, `struct drm_etnaviv_pm_domain`, `struct drm_etnaviv_pm_signal`, `struct etnaviv_perfmon_request`.
• 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.