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

File Facts

System

Linux kernel

Corpus path

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

Extension

.c

Size

40153 bytes

Lines

1522

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.
• 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/crc32.h
• linux/delay.h
• linux/dmaengine.h
• linux/io.h
• linux/module.h
• linux/msi.h
• linux/slab.h
• linux/pci_ids.h
• linux/random.h
• linux/pci-epc.h
• linux/pci-epf.h
• linux/pci-ep-msi.h
• linux/pci_regs.h

Detected Declarations

• struct pci_epf_test
• struct pci_epf_test_reg
• struct epf_dma_filter
• function pci_epf_test_dma_callback
• function pci_epf_test_data_transfer
• function epf_dma_filter_fn
• function pci_epf_test_init_dma_chan
• function pci_epf_test_clean_dma_chan
• function pci_epf_test_print_rate
• function pci_epf_test_copy
• function pci_epf_test_read
• function pci_epf_test_write
• function pci_epf_test_raise_irq
• function pci_epf_test_doorbell_handler
• function pci_epf_test_doorbell_cleanup
• function pci_epf_test_enable_doorbell
• function pci_epf_test_disable_doorbell
• function pci_epf_test_subrange_sig_byte
• function pci_epf_test_bar_subrange_setup
• function pci_epf_test_bar_subrange_clear
• function pci_epf_test_cmd_handler
• function pci_epf_test_set_bar
• function pci_epf_test_clear_bar
• function pci_epf_test_set_capabilities
• function pci_epf_test_epc_init
• function pci_epf_test_epc_deinit
• function pci_epf_test_link_up
• function pci_epf_test_link_down
• function pci_epf_test_alloc_space
• function pci_epf_test_free_space
• function pci_epf_test_bind
• function pci_epf_test_unbind
• function pci_epf_test_probe
• function pci_epf_test_init
• function pci_epf_test_exit
• module init pci_epf_test_init

Annotated Snippet

module_init(pci_epf_test_init);

static void __exit pci_epf_test_exit(void)
{
	if (kpcitest_workqueue)
		destroy_workqueue(kpcitest_workqueue);
	pci_epf_unregister_driver(&test_driver);
}
module_exit(pci_epf_test_exit);

MODULE_DESCRIPTION("PCI EPF TEST DRIVER");
MODULE_AUTHOR("Kishon Vijay Abraham I <kishon@ti.com>");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/crc32.h`, `linux/delay.h`, `linux/dmaengine.h`, `linux/io.h`, `linux/module.h`, `linux/msi.h`, `linux/slab.h`, `linux/pci_ids.h`.
• Detected declarations: `struct pci_epf_test`, `struct pci_epf_test_reg`, `struct epf_dma_filter`, `function pci_epf_test_dma_callback`, `function pci_epf_test_data_transfer`, `function epf_dma_filter_fn`, `function pci_epf_test_init_dma_chan`, `function pci_epf_test_clean_dma_chan`, `function pci_epf_test_print_rate`, `function pci_epf_test_copy`.
• Atlas domain: Representative Device Path / PCIe NVMe Storage Path.
• 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.