drivers/usb/dwc2/pci.c
Source file repositories/reference/linux-study-clean/drivers/usb/dwc2/pci.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/usb/dwc2/pci.c- Extension
.c- Size
- 2990 bytes
- Lines
- 137
- 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.hlinux/module.hlinux/moduleparam.hlinux/spinlock.hlinux/interrupt.hlinux/io.hlinux/slab.hlinux/pci.hlinux/usb.hlinux/usb/hcd.hlinux/usb/ch11.hlinux/platform_device.hlinux/usb/usb_phy_generic.hcore.h
Detected Declarations
struct dwc2_pci_gluefunction dwc2_pci_removefunction dwc2_pci_probe
Annotated Snippet
static struct pci_driver dwc2_pci_driver = {
.name = dwc2_driver_name,
.id_table = dwc2_pci_ids,
.probe = dwc2_pci_probe,
.remove = dwc2_pci_remove,
};
module_pci_driver(dwc2_pci_driver);
MODULE_DESCRIPTION("DESIGNWARE HS OTG PCI Bus Glue");
MODULE_AUTHOR("Synopsys, Inc.");
MODULE_LICENSE("Dual BSD/GPL");Annotation
- Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/moduleparam.h`, `linux/spinlock.h`, `linux/interrupt.h`, `linux/io.h`, `linux/slab.h`, `linux/pci.h`.
- Detected declarations: `struct dwc2_pci_glue`, `function dwc2_pci_remove`, `function dwc2_pci_probe`.
- 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.