drivers/usb/cdns3/cdns3-pci-wrap.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/cdns3/cdns3-pci-wrap.c

Extension

.c

Size

5354 bytes

Lines

204

Domain

Driver Families

Bucket

drivers/usb

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.
• 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/kernel.h
• linux/module.h
• linux/pci.h
• linux/platform_device.h
• linux/dma-mapping.h
• linux/slab.h

Detected Declarations

• struct cdns3_wrap
• function cdns3_pci_probe
• function cdns3_pci_remove

Annotated Snippet

static struct pci_driver cdns3_pci_driver = {
	.name = PCI_DRIVER_NAME,
	.id_table = cdns3_pci_ids,
	.probe = cdns3_pci_probe,
	.remove = cdns3_pci_remove,
};

module_pci_driver(cdns3_pci_driver);
MODULE_DEVICE_TABLE(pci, cdns3_pci_ids);

MODULE_AUTHOR("Pawel Laszczak <pawell@cadence.com>");
MODULE_LICENSE("GPL v2");
MODULE_DESCRIPTION("Cadence USBSS PCI wrapper");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/pci.h`, `linux/platform_device.h`, `linux/dma-mapping.h`, `linux/slab.h`.
• Detected declarations: `struct cdns3_wrap`, `function cdns3_pci_probe`, `function cdns3_pci_remove`.
• Atlas domain: Driver Families / drivers/usb.
• 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.