drivers/usb/host/xhci.c
Source file repositories/reference/linux-study-clean/drivers/usb/host/xhci.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/usb/host/xhci.c- Extension
.c- Size
- 171929 bytes
- Lines
- 5721
- Domain
- Driver Families
- Bucket
- drivers/usb
- Inferred role
- Driver Families: exported/initcall integration point
- Status
- integration 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.
- 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.
- 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/jiffies.hlinux/pci.hlinux/iommu.hlinux/iopoll.hlinux/irq.hlinux/log2.hlinux/module.hlinux/moduleparam.hlinux/slab.hlinux/string_choices.hlinux/dmi.hlinux/dma-mapping.hlinux/usb/xhci-sideband.hxhci.hxhci-trace.hxhci-debugfs.hxhci-dbgcap.h
Detected Declarations
function xhci_portsc_writelfunction xhci_portsc_readlfunction td_on_ringfunction xhci_for_each_ring_segfunction xhci_handshakefunction xhci_quiescefunction xhci_haltfunction xhci_startfunction xhci_resetfunction xhci_zero_64b_regsfunction xhci_enable_interrupterfunction xhci_disable_interrupterfunction xhci_set_interrupter_moderationfunction compliance_mode_recoveryfunction modefunction xhci_compliance_mode_recovery_timer_quirk_checkfunction xhci_all_ports_seen_u0function xhci_hcd_page_sizefunction xhci_enable_max_dev_slotsfunction xhci_set_cmd_ring_deqfunction xhci_set_doorbell_ptrfunction xhci_set_dev_notificationsfunction xhci_initfunction xhci_run_finishedfunction xhci_stopfunction xhci_runfunction HCfunction xhci_save_registersfunction xhci_restore_registersfunction ringfunction enumeratedfunction xhci_pending_porteventfunction HCfunction BITfunction xHCfunction xhci_map_temp_bufferfunction xhci_urb_temp_buffer_requiredfunction xhci_unmap_temp_buffunction Transferfunction xhci_unmap_urb_for_dmafunction xhci_get_endpoint_indexfunction xhci_get_endpoint_addressfunction xhci_get_endpoint_flagfunction flsfunction xhci_check_argsfunction xhci_check_ep0_maxpacketfunction ownerfunction usb_hcd_unlink_urb
Annotated Snippet
module_init(xhci_hcd_init);
module_exit(xhci_hcd_fini);
Annotation
- Immediate include surface: `linux/jiffies.h`, `linux/pci.h`, `linux/iommu.h`, `linux/iopoll.h`, `linux/irq.h`, `linux/log2.h`, `linux/module.h`, `linux/moduleparam.h`.
- Detected declarations: `function xhci_portsc_writel`, `function xhci_portsc_readl`, `function td_on_ring`, `function xhci_for_each_ring_seg`, `function xhci_handshake`, `function xhci_quiesce`, `function xhci_halt`, `function xhci_start`, `function xhci_reset`, `function xhci_zero_64b_regs`.
- Atlas domain: Driver Families / drivers/usb.
- 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.