drivers/pci/endpoint/functions/pci-epf-mhi.c

File Facts

System

Linux kernel

Corpus path

drivers/pci/endpoint/functions/pci-epf-mhi.c

Extension

.c

Size

26559 bytes

Lines

996

Domain

Representative Device Path

Bucket

PCIe NVMe Storage Path

Inferred role

Representative Device Path: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.

• Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.
• 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/dmaengine.h
• linux/mhi_ep.h
• linux/module.h
• linux/of_dma.h
• linux/platform_device.h
• linux/pci-epc.h
• linux/pci-epf.h

Detected Declarations

• struct pci_epf_mhi_dma_transfer
• struct pci_epf_mhi_ep_info
• struct pci_epf_mhi
• struct epf_dma_filter
• function get_align_offset
• function __pci_epf_mhi_alloc_map
• function pci_epf_mhi_alloc_map
• function __pci_epf_mhi_unmap_free
• function pci_epf_mhi_unmap_free
• function pci_epf_mhi_raise_irq
• function pci_epf_mhi_iatu_read
• function pci_epf_mhi_iatu_write
• function pci_epf_mhi_dma_callback
• function pci_epf_mhi_edma_read
• function pci_epf_mhi_edma_write
• function pci_epf_mhi_dma_worker
• function list_for_each_entry_safe
• function pci_epf_mhi_dma_async_callback
• function pci_epf_mhi_edma_read_async
• function pci_epf_mhi_edma_write_async
• function pci_epf_mhi_filter
• function pci_epf_mhi_dma_init
• function pci_epf_mhi_dma_deinit
• function pci_epf_mhi_epc_init
• function pci_epf_mhi_epc_deinit
• function pci_epf_mhi_link_up
• function pci_epf_mhi_link_down
• function pci_epf_mhi_bus_master_enable
• function pci_epf_mhi_bind
• function pci_epf_mhi_unbind
• function pci_epf_mhi_probe
• function pci_epf_mhi_init
• function pci_epf_mhi_exit
• module init pci_epf_mhi_init

Annotated Snippet

module_init(pci_epf_mhi_init);

static void __exit pci_epf_mhi_exit(void)
{
	pci_epf_unregister_driver(&pci_epf_mhi_driver);
}
module_exit(pci_epf_mhi_exit);

MODULE_DESCRIPTION("PCI EPF driver for MHI Endpoint devices");
MODULE_AUTHOR("Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/dmaengine.h`, `linux/mhi_ep.h`, `linux/module.h`, `linux/of_dma.h`, `linux/platform_device.h`, `linux/pci-epc.h`, `linux/pci-epf.h`.
• Detected declarations: `struct pci_epf_mhi_dma_transfer`, `struct pci_epf_mhi_ep_info`, `struct pci_epf_mhi`, `struct epf_dma_filter`, `function get_align_offset`, `function __pci_epf_mhi_alloc_map`, `function pci_epf_mhi_alloc_map`, `function __pci_epf_mhi_unmap_free`, `function pci_epf_mhi_unmap_free`, `function pci_epf_mhi_raise_irq`.
• Atlas domain: Representative Device Path / PCIe NVMe Storage Path.
• 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.