include/linux/of_iommu.h

File Facts

System

Linux kernel

Corpus path

include/linux/of_iommu.h

Extension

.h

Size

671 bytes

Lines

34

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct device
• struct device_node
• struct iommu_ops
• function of_iommu_configure
• function of_iommu_get_resv_regions

Annotated Snippet

#ifndef __OF_IOMMU_H
#define __OF_IOMMU_H

struct device;
struct device_node;
struct iommu_ops;

#ifdef CONFIG_OF_IOMMU

extern int of_iommu_configure(struct device *dev, struct device_node *master_np,
			      const u32 *id);

extern void of_iommu_get_resv_regions(struct device *dev,
				      struct list_head *list);

#else

static inline int of_iommu_configure(struct device *dev,
				     struct device_node *master_np,
				     const u32 *id)
{
	return -ENODEV;
}

static inline void of_iommu_get_resv_regions(struct device *dev,
					     struct list_head *list)
{
}

#endif	/* CONFIG_OF_IOMMU */

#endif /* __OF_IOMMU_H */

Annotation

• Detected declarations: `struct device`, `struct device_node`, `struct iommu_ops`, `function of_iommu_configure`, `function of_iommu_get_resv_regions`.
• 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.