drivers/iommu/omap-iommu.c

File Facts

System

Linux kernel

Corpus path

drivers/iommu/omap-iommu.c

Extension

.c

Size

41987 bytes

Lines

1767

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/dma-mapping.h
• linux/err.h
• linux/slab.h
• linux/interrupt.h
• linux/ioport.h
• linux/platform_device.h
• linux/iommu.h
• linux/omap-iommu.h
• linux/mutex.h
• linux/spinlock.h
• linux/io.h
• linux/pm_runtime.h
• linux/of.h
• linux/of_irq.h
• linux/of_platform.h
• linux/regmap.h
• linux/mfd/syscon.h
• linux/platform_data/iommu-omap.h
• omap-iopgtable.h
• omap-iommu.h

Detected Declarations

• function omap_iommu_save_ctx
• function omap_iommu_restore_ctx
• function dra7_cfg_dspsys_mmu
• function __iommu_set_twl
• function omap2_iommu_enable
• function omap2_iommu_disable
• function iommu_enable
• function iommu_disable
• function iotlb_cr_to_virt
• function get_iopte_attr
• function iommu_report_fault
• function iotlb_lock_get
• function iotlb_lock_set
• function iotlb_read_cr
• function iotlb_load_cr
• function __iotlb_read_cr
• function load_iotlb_entry
• function load_iotlb_entry
• function prefetch_iotlb_entry
• function flush_iotlb_page
• function for_each_iotlb_cr
• function flush_iotlb_all
• function flush_iopte_range
• function iopte_free
• function iopgd_alloc_section
• function iopgd_alloc_super
• function iopte_alloc_page
• function iopte_alloc_large
• function iopgtable_store_entry_core
• function omap_iopgtable_store_entry
• function iopgtable_lookup_entry
• function iopgtable_clear_entry_core
• function iopgtable_clear_entry
• function iopgtable_clear_entry_all
• function iommu_fault_handler
• function omap_iommu_attach
• function omap_iommu_detach
• function omap_iommu_save_tlb_entries
• function omap_iommu_restore_tlb_entries
• function omap_iommu_domain_deactivate
• function omap_iommu_domain_activate
• function omap_iommu_runtime_suspend
• function omap_iommu_runtime_resume
• function omap_iommu_prepare
• function omap_iommu_can_register
• function omap_iommu_dra7_get_dsp_system_cfg
• function MMU
• function omap_iommu_remove

Annotated Snippet

subsys_initcall(omap_iommu_init);
/* must be ready before omap3isp is probed */

Annotation

• Immediate include surface: `linux/dma-mapping.h`, `linux/err.h`, `linux/slab.h`, `linux/interrupt.h`, `linux/ioport.h`, `linux/platform_device.h`, `linux/iommu.h`, `linux/omap-iommu.h`.
• Detected declarations: `function omap_iommu_save_ctx`, `function omap_iommu_restore_ctx`, `function dra7_cfg_dspsys_mmu`, `function __iommu_set_twl`, `function omap2_iommu_enable`, `function omap2_iommu_disable`, `function iommu_enable`, `function iommu_disable`, `function iotlb_cr_to_virt`, `function get_iopte_attr`.
• 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.