include/linux/platform_data/amd_qdma.h

File Facts

System

Linux kernel

Corpus path

include/linux/platform_data/amd_qdma.h

Extension

.h

Size

943 bytes

Lines

39

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/dmaengine.h

Detected Declarations

• struct qdma_queue_info
• struct dma_slave_map
• struct qdma_platdata

Annotated Snippet

struct qdma_queue_info {
	enum dma_transfer_direction dir;
};

#define QDMA_FILTER_PARAM(qinfo)	((void *)(qinfo))

struct dma_slave_map;

/**
 * struct qdma_platdata - Platform specific data for QDMA engine
 * @max_mm_channels: Maximum number of MM DMA channels in each direction
 * @device_map: DMA slave map
 * @irq_index: The index of first IRQ
 * @dma_dev: The device pointer for dma operations
 */
struct qdma_platdata {
	u32			max_mm_channels;
	u32			irq_index;
	struct dma_slave_map	*device_map;
	struct device		*dma_dev;
};

#endif /* _PLATDATA_AMD_QDMA_H */

Annotation

• Immediate include surface: `linux/dmaengine.h`.
• Detected declarations: `struct qdma_queue_info`, `struct dma_slave_map`, `struct qdma_platdata`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.