drivers/ufs/host/tc-dwc-g210-pci.c

File Facts

System

Linux kernel

Corpus path

drivers/ufs/host/tc-dwc-g210-pci.c

Extension

.c

Size

3487 bytes

Lines

139

Domain

Driver Families

Bucket

drivers/ufs

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• ufs/ufshcd.h
• ufshcd-dwc.h
• tc-dwc-g210.h
• linux/module.h
• linux/pci.h
• linux/pm_runtime.h

Detected Declarations

• function tc_dwc_g210_pci_remove
• function tc_dwc_g210_pci_probe

Annotated Snippet

static struct pci_driver tc_dwc_g210_pci_driver = {
	.name = "tc-dwc-g210-pci",
	.id_table = tc_dwc_g210_pci_tbl,
	.probe = tc_dwc_g210_pci_probe,
	.remove = tc_dwc_g210_pci_remove,
	.driver = {
		.pm = &tc_dwc_g210_pci_pm_ops
	},
};

module_pci_driver(tc_dwc_g210_pci_driver);

MODULE_AUTHOR("Joao Pinto <Joao.Pinto@synopsys.com>");
MODULE_DESCRIPTION("Synopsys Test Chip G210 PCI glue driver");
MODULE_LICENSE("Dual BSD/GPL");

Annotation

• Immediate include surface: `ufs/ufshcd.h`, `ufshcd-dwc.h`, `tc-dwc-g210.h`, `linux/module.h`, `linux/pci.h`, `linux/pm_runtime.h`.
• Detected declarations: `function tc_dwc_g210_pci_remove`, `function tc_dwc_g210_pci_probe`.
• Atlas domain: Driver Families / drivers/ufs.
• Implementation status: pattern implementation candidate.

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.