drivers/pci/controller/pcie-rcar-host.c
Source file repositories/reference/linux-study-clean/drivers/pci/controller/pcie-rcar-host.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/pci/controller/pcie-rcar-host.c- Extension
.c- Size
- 29474 bytes
- Lines
- 1142
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/bitops.hlinux/cleanup.hlinux/clk.hlinux/clk-provider.hlinux/delay.hlinux/interrupt.hlinux/irq.hlinux/irqchip/irq-msi-lib.hlinux/irqdomain.hlinux/kernel.hlinux/init.hlinux/iopoll.hlinux/msi.hlinux/of_address.hlinux/of_irq.hlinux/of_platform.hlinux/pci.hlinux/phy/phy.hlinux/platform_device.hlinux/pm_runtime.hlinux/regulator/consumer.hpcie-rcar.h
Detected Declarations
struct rcar_msistruct rcar_pcie_hostfunction rcar_pcie_wakeupfunction rcar_read_conffunction rcar_pci_write_reg_workaroundfunction rcar_pci_read_reg_workaroundfunction rcar_pcie_config_accessfunction rcar_pcie_read_conffunction rcar_pcie_write_conffunction rcar_pcie_force_speedupfunction rcar_pcie_hw_enablefunction rcar_pcie_enablefunction phy_wait_for_ackfunction phy_write_regfunction rcar_pcie_hw_initfunction rcar_pcie_phy_init_h1function rcar_pcie_phy_init_gen2function rcar_pcie_phy_init_gen3function rcar_pcie_msi_irqfunction rcar_msi_irq_ackfunction rcar_msi_irq_maskfunction scoped_guardfunction rcar_msi_irq_unmaskfunction scoped_guardfunction rcar_compose_msi_msgfunction rcar_msi_domain_allocfunction rcar_msi_domain_freefunction rcar_allocate_domainsfunction rcar_free_domainsfunction rcar_pcie_enable_msifunction rcar_pcie_teardown_msifunction rcar_pcie_get_resourcesfunction rcar_pcie_inbound_rangesfunction rcar_pcie_parse_map_dma_rangesfunction resource_list_for_each_entryfunction rcar_pcie_probefunction rcar_pcie_resumefunction rcar_pcie_resume_noirqfunction rcar_pcie_aarch32_abort_handlerfunction rcar_pcie_initmodule init rcar_pcie_init
Annotated Snippet
device_initcall(rcar_pcie_init);
#else
builtin_platform_driver(rcar_pcie_driver);
#endifAnnotation
- Immediate include surface: `linux/bitops.h`, `linux/cleanup.h`, `linux/clk.h`, `linux/clk-provider.h`, `linux/delay.h`, `linux/interrupt.h`, `linux/irq.h`, `linux/irqchip/irq-msi-lib.h`.
- Detected declarations: `struct rcar_msi`, `struct rcar_pcie_host`, `function rcar_pcie_wakeup`, `function rcar_read_conf`, `function rcar_pci_write_reg_workaround`, `function rcar_pci_read_reg_workaround`, `function rcar_pcie_config_access`, `function rcar_pcie_read_conf`, `function rcar_pcie_write_conf`, `function rcar_pcie_force_speedup`.
- 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.