drivers/iommu/exynos-iommu.c

File Facts

System

Linux kernel

Corpus path

drivers/iommu/exynos-iommu.c

Extension

.c

Size

42819 bytes

Lines

1532

Domain

Driver Families

Bucket

drivers/iommu

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/clk.h
• linux/dma-mapping.h
• linux/err.h
• linux/io.h
• linux/iommu.h
• linux/interrupt.h
• linux/kmemleak.h
• linux/list.h
• linux/of.h
• linux/of_platform.h
• linux/platform_device.h
• linux/pm_runtime.h
• linux/slab.h
• dma-iommu.h
• iommu-pages.h

Detected Declarations

• struct sysmmu_fault
• struct sysmmu_v1_fault_info
• struct exynos_iommu_owner
• struct exynos_iommu_domain
• struct sysmmu_drvdata
• struct sysmmu_variant
• struct sysmmu_drvdata
• function lv1ent_offset
• function lv2ent_offset
• function exynos_sysmmu_v1_get_fault_info
• function exynos_sysmmu_v5_get_fault_info
• function exynos_sysmmu_v7_get_fault_info
• function sysmmu_unblock
• function sysmmu_block
• function __sysmmu_tlb_invalidate
• function __sysmmu_tlb_invalidate_entry
• function __sysmmu_set_ptbase
• function __sysmmu_enable_clocks
• function __sysmmu_disable_clocks
• function __sysmmu_has_capa1
• function __sysmmu_get_vcr
• function __sysmmu_get_version
• function show_fault_information
• function exynos_sysmmu_irq
• function __sysmmu_disable
• function __sysmmu_init_config
• function __sysmmu_enable_vid
• function __sysmmu_enable
• function sysmmu_tlb_invalidate_flpdcache
• function sysmmu_tlb_invalidate_entry
• function exynos_sysmmu_probe
• function exynos_sysmmu_suspend
• function exynos_sysmmu_resume
• function exynos_iommu_set_pte
• function exynos_iommu_domain_free
• function list_for_each_entry_safe
• function exynos_iommu_identity_attach
• function list_for_each_entry
• function exynos_iommu_attach_device
• function list_for_each_entry
• function lv1set_section
• function lv2set_page
• function exynos_iommu_map
• function exynos_iommu_tlb_invalidate_entry
• function exynos_iommu_unmap
• function exynos_iommu_iova_to_phys
• function list_for_each_entry
• function exynos_iommu_release_device

Annotated Snippet

core_initcall(exynos_iommu_init);

Annotation

• Immediate include surface: `linux/clk.h`, `linux/dma-mapping.h`, `linux/err.h`, `linux/io.h`, `linux/iommu.h`, `linux/interrupt.h`, `linux/kmemleak.h`, `linux/list.h`.
• Detected declarations: `struct sysmmu_fault`, `struct sysmmu_v1_fault_info`, `struct exynos_iommu_owner`, `struct exynos_iommu_domain`, `struct sysmmu_drvdata`, `struct sysmmu_variant`, `struct sysmmu_drvdata`, `function lv1ent_offset`, `function lv2ent_offset`, `function exynos_sysmmu_v1_get_fault_info`.
• Atlas domain: Driver Families / drivers/iommu.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.