drivers/iommu/io-pgtable-arm-v7s.c

File Facts

System

Linux kernel

Corpus path

drivers/iommu/io-pgtable-arm-v7s.c

Extension

.c

Size

25352 bytes

Lines

910

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.
• 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/dma-mapping.h
• linux/gfp.h
• linux/io-pgtable.h
• linux/iommu.h
• linux/kernel.h
• linux/kmemleak.h
• linux/sizes.h
• linux/slab.h
• linux/spinlock.h
• linux/types.h
• asm/barrier.h

Detected Declarations

• struct arm_v7s_io_pgtable
• function __arm_v7s_dma_addr
• function arm_v7s_is_mtk_enabled
• function to_mtk_iopte
• function paddr_to_iopte
• function iopte_to_paddr
• function __arm_v7s_free_table
• function __arm_v7s_pte_sync
• function __arm_v7s_set_pte
• function arm_v7s_prot_to_pte
• function arm_v7s_pte_to_cont
• function arm_v7s_pte_is_cont
• function arm_v7s_init_pte
• function arm_v7s_install_table
• function __arm_v7s_map
• function arm_v7s_map_pages
• function arm_v7s_free_pgtable
• function __arm_v7s_unmap
• function arm_v7s_unmap_pages
• function arm_v7s_iova_to_phys
• function __arm_v7s_unmap
• function dummy_tlb_flush
• function dummy_tlb_add_page
• function arm_v7s_do_selftests
• module init arm_v7s_do_selftests

Annotated Snippet

subsys_initcall(arm_v7s_do_selftests);
#endif

Annotation

• Immediate include surface: `linux/atomic.h`, `linux/dma-mapping.h`, `linux/gfp.h`, `linux/io-pgtable.h`, `linux/iommu.h`, `linux/kernel.h`, `linux/kmemleak.h`, `linux/sizes.h`.
• Detected declarations: `struct arm_v7s_io_pgtable`, `function __arm_v7s_dma_addr`, `function arm_v7s_is_mtk_enabled`, `function to_mtk_iopte`, `function paddr_to_iopte`, `function iopte_to_paddr`, `function __arm_v7s_free_table`, `function __arm_v7s_pte_sync`, `function __arm_v7s_set_pte`, `function arm_v7s_prot_to_pte`.
• Atlas domain: Driver Families / drivers/iommu.
• Implementation status: integration implementation candidate.
• 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.