drivers/usb/host/ehci-hcd.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/host/ehci-hcd.c

Extension

.c

Size

38779 bytes

Lines

1402

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/module.h
• linux/pci.h
• linux/dmapool.h
• linux/kernel.h
• linux/delay.h
• linux/ioport.h
• linux/sched.h
• linux/vmalloc.h
• linux/errno.h
• linux/init.h
• linux/hrtimer.h
• linux/list.h
• linux/interrupt.h
• linux/usb.h
• linux/usb/hcd.h
• linux/usb/otg.h
• linux/moduleparam.h
• linux/dma-mapping.h
• linux/debugfs.h
• linux/platform_device.h
• linux/slab.h
• asm/byteorder.h
• asm/io.h
• asm/irq.h
• linux/unaligned.h
• asm/firmware.h
• ehci.h
• pci-quirks.h
• ehci-dbg.c
• ehci-timer.c
• ehci-hub.c
• ehci-mem.c

Detected Declarations

• function ehci_moschip_read_frame_index
• function ehci_read_frame_index
• function ehci_handshake
• function tdi_in_host_mode
• function unknown
• function tdi_reset
• function ehci_reset
• function controller
• function ehci_turn_off_all_ports
• function ehci_silence_controller
• function ehci_shutdown
• function ehci_work
• function ehci_stop
• function ehci_init
• function ehci_run
• function ehci_setup
• function ehci_irq
• function owner
• function ehci_urb_dequeue
• function ehci_endpoint_disable
• function ehci_endpoint_reset
• function usb_clear_halt
• function ehci_get_frame
• function ehci_remove_device
• function ehci_zx_wakeup_clear
• function ehci_suspend
• function ehci_resume
• function ehci_suspend
• function ehci_init_driver
• function ehci_hcd_init
• function ehci_hcd_cleanup
• module init ehci_hcd_init
• export ehci_handshake
• export ehci_reset
• export ehci_setup
• export ehci_suspend
• export ehci_resume
• export ehci_init_driver

Annotated Snippet

module_init(ehci_hcd_init);

static void __exit ehci_hcd_cleanup(void)
{
#ifdef CONFIG_PPC_PS3
	ps3_ehci_driver_unregister(&ps3_ehci_driver);
#endif
	platform_unregister_drivers(platform_drivers, ARRAY_SIZE(platform_drivers));
#ifdef CONFIG_DYNAMIC_DEBUG
	debugfs_remove(ehci_debug_root);
#endif
}
module_exit(ehci_hcd_cleanup);

Annotation

• Immediate include surface: `linux/module.h`, `linux/pci.h`, `linux/dmapool.h`, `linux/kernel.h`, `linux/delay.h`, `linux/ioport.h`, `linux/sched.h`, `linux/vmalloc.h`.
• Detected declarations: `function ehci_moschip_read_frame_index`, `function ehci_read_frame_index`, `function ehci_handshake`, `function tdi_in_host_mode`, `function unknown`, `function tdi_reset`, `function ehci_reset`, `function controller`, `function ehci_turn_off_all_ports`, `function ehci_silence_controller`.
• 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.