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

File Facts

System

Linux kernel

Corpus path

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

Extension

.h

Size

1926 bytes

Lines

47

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 amdgpu_lsdma
• struct amdgpu_lsdma_funcs

Annotated Snippet

struct amdgpu_lsdma {
	const struct amdgpu_lsdma_funcs      *funcs;
};

struct amdgpu_lsdma_funcs {
	int (*copy_mem)(struct amdgpu_device *adev, uint64_t src_addr,
			uint64_t dst_addr, uint64_t size);
	int (*fill_mem)(struct amdgpu_device *adev, uint64_t dst_addr,
			uint32_t data, uint64_t size);
	void (*update_memory_power_gating)(struct amdgpu_device *adev, bool enable);
};

int amdgpu_lsdma_copy_mem(struct amdgpu_device *adev, uint64_t src_addr,
			  uint64_t dst_addr, uint64_t mem_size);
int amdgpu_lsdma_fill_mem(struct amdgpu_device *adev, uint64_t dst_addr,
			  uint32_t data, uint64_t mem_size);
int amdgpu_lsdma_wait_for(struct amdgpu_device *adev, uint32_t reg_index,
			  uint32_t reg_val, uint32_t mask);

#endif

Annotation

• Detected declarations: `struct amdgpu_lsdma`, `struct amdgpu_lsdma_funcs`.
• 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.