drivers/pci/controller/dwc/pci-imx6.c

File Facts

System

Linux kernel

Corpus path

drivers/pci/controller/dwc/pci-imx6.c

Extension

.c

Size

60299 bytes

Lines

2118

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/bitfield.h
• linux/clk.h
• linux/delay.h
• linux/gpio/consumer.h
• linux/kernel.h
• linux/mfd/syscon.h
• linux/mfd/syscon/imx6q-iomuxc-gpr.h
• linux/mfd/syscon/imx7-iomuxc-gpr.h
• linux/module.h
• linux/of.h
• linux/of_address.h
• linux/pci.h
• linux/platform_device.h
• linux/regmap.h
• linux/regulator/consumer.h
• linux/resource.h
• linux/signal.h
• linux/types.h
• linux/interrupt.h
• linux/reset.h
• linux/phy/pcie.h
• linux/phy/phy.h
• linux/pm_domain.h
• linux/pm_runtime.h
• ../../pci.h
• pcie-designware.h

Detected Declarations

• struct imx_pcie
• struct imx_pcie_drvdata
• struct imx_lut_data
• struct imx_pcie
• enum imx_pcie_variants
• function imx_pcie_grp_offset
• function imx95_pcie_init_phy
• function imx_pcie_configure_type
• function pcie_phy_poll_ack
• function pcie_phy_wait_ack
• function pcie_phy_read
• function pcie_phy_write
• function imx8mq_pcie_init_phy
• function imx_pcie_init_phy
• function imx6sx_pcie_init_phy
• function imx7d_pcie_wait_for_phy_pll_lock
• function imx95_pcie_wait_for_phy_pll_lock
• function imx_setup_phy_mpll
• function imx_pcie_reset_phy
• function imx6q_pcie_abort_handler
• function imx_pcie_attach_pd
• function imx6sx_pcie_enable_ref_clk
• function imx6q_pcie_enable_ref_clk
• function imx8mm_pcie_clkreq_override
• function imx8mm_pcie_enable_ref_clk
• function imx7d_pcie_enable_ref_clk
• function imx95_pcie_clkreq_override
• function imx95_pcie_enable_ref_clk
• function imx8mm_pcie_clr_clkreq_override
• function imx95_pcie_clr_clkreq_override
• function imx_pcie_clk_enable
• function imx_pcie_clk_disable
• function imx6sx_pcie_core_reset
• function imx6qp_pcie_core_reset
• function imx6q_pcie_core_reset
• function imx7d_pcie_core_reset
• function ERR010728
• function imx95_pcie_core_reset
• function imx_pcie_assert_core_reset
• function imx_pcie_deassert_core_reset
• function imx_pcie_wait_for_speed_change
• function imx_pcie_ltssm_enable
• function imx_pcie_ltssm_disable
• function imx_pcie_start_link
• function imx_pcie_stop_link
• function imx_pcie_add_lut
• function imx_pcie_remove_lut
• function imx_pcie_add_lut_by_rid

Annotated Snippet

device_initcall(imx_pcie_init);

Annotation

• Immediate include surface: `linux/bitfield.h`, `linux/clk.h`, `linux/delay.h`, `linux/gpio/consumer.h`, `linux/kernel.h`, `linux/mfd/syscon.h`, `linux/mfd/syscon/imx6q-iomuxc-gpr.h`, `linux/mfd/syscon/imx7-iomuxc-gpr.h`.
• Detected declarations: `struct imx_pcie`, `struct imx_pcie_drvdata`, `struct imx_lut_data`, `struct imx_pcie`, `enum imx_pcie_variants`, `function imx_pcie_grp_offset`, `function imx95_pcie_init_phy`, `function imx_pcie_configure_type`, `function pcie_phy_poll_ack`, `function pcie_phy_wait_ack`.
• 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.