drivers/iommu/arm/arm-smmu/qcom_iommu.c

File Facts

System

Linux kernel

Corpus path

drivers/iommu/arm/arm-smmu/qcom_iommu.c

Extension

.c

Size

24320 bytes

Lines

945

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/atomic.h
• linux/bitfield.h
• linux/clk.h
• linux/delay.h
• linux/dma-mapping.h
• linux/err.h
• linux/interrupt.h
• linux/io.h
• linux/io-64-nonatomic-hi-lo.h
• linux/io-pgtable.h
• linux/iommu.h
• linux/iopoll.h
• linux/kconfig.h
• linux/init.h
• linux/mutex.h
• linux/of.h
• linux/of_platform.h
• linux/platform_device.h
• linux/pm.h
• linux/pm_runtime.h
• linux/firmware/qcom/qcom_scm.h
• linux/slab.h
• linux/spinlock.h
• arm-smmu.h

Detected Declarations

• struct qcom_iommu_ctx
• struct qcom_iommu_dev
• struct qcom_iommu_ctx
• struct qcom_iommu_domain
• enum qcom_iommu_clk
• function to_ctx
• function iommu_writel
• function iommu_writeq
• function iommu_readl
• function iommu_readq
• function qcom_iommu_tlb_sync
• function qcom_iommu_tlb_inv_context
• function qcom_iommu_tlb_inv_range_nosync
• function qcom_iommu_tlb_flush_walk
• function qcom_iommu_tlb_add_page
• function qcom_iommu_fault
• function qcom_iommu_init_domain
• function qcom_iommu_domain_free
• function qcom_iommu_attach_dev
• function qcom_iommu_identity_attach
• function qcom_iommu_map
• function qcom_iommu_unmap
• function qcom_iommu_flush_iotlb_all
• function qcom_iommu_iotlb_sync
• function qcom_iommu_iova_to_phys
• function qcom_iommu_capable
• function qcom_iommu_of_xlate
• function qcom_iommu_sec_ptbl_init
• function get_asid
• function qcom_iommu_ctx_probe
• function qcom_iommu_ctx_remove
• function qcom_iommu_has_secure_context
• function qcom_iommu_device_probe
• function qcom_iommu_device_remove
• function qcom_iommu_resume
• function qcom_iommu_suspend
• function qcom_iommu_init
• module init qcom_iommu_init

Annotated Snippet

device_initcall(qcom_iommu_init);

Annotation

• Immediate include surface: `linux/atomic.h`, `linux/bitfield.h`, `linux/clk.h`, `linux/delay.h`, `linux/dma-mapping.h`, `linux/err.h`, `linux/interrupt.h`, `linux/io.h`.
• Detected declarations: `struct qcom_iommu_ctx`, `struct qcom_iommu_dev`, `struct qcom_iommu_ctx`, `struct qcom_iommu_domain`, `enum qcom_iommu_clk`, `function to_ctx`, `function iommu_writel`, `function iommu_writeq`, `function iommu_readl`, `function iommu_readq`.
• 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.