drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.h

Extension

.h

Size

2058 bytes

Lines

57

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/debugfs.h

Detected Declarations

• struct ip_discovery_top
• struct drm_printer
• struct amdgpu_discovery_info

Annotated Snippet

struct amdgpu_discovery_info {
	struct debugfs_blob_wrapper debugfs_blob;
	struct ip_discovery_top *ip_top;
	uint64_t offset;
	uint32_t size;
	uint8_t *bin;
	bool reserve_tmr;
};

void amdgpu_discovery_fini(struct amdgpu_device *adev);
int amdgpu_discovery_set_ip_blocks(struct amdgpu_device *adev);

int amdgpu_discovery_get_nps_info(struct amdgpu_device *adev,
				  uint32_t *nps_type,
				  struct amdgpu_gmc_memrange *ranges,
				  int *range_cnt, bool refresh);
int amdgpu_discovery_get_gc_major_minor_version(struct amdgpu_device *adev,
						uint16_t *major, uint16_t *minor);

void amdgpu_discovery_dump(struct amdgpu_device *adev, struct drm_printer *p);

#endif /* __AMDGPU_DISCOVERY__ */

Annotation

• Immediate include surface: `linux/debugfs.h`.
• Detected declarations: `struct ip_discovery_top`, `struct drm_printer`, `struct amdgpu_discovery_info`.
• 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.