drivers/usb/host/ohci-hcd.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/host/ohci-hcd.c

Extension

.c

Size

36431 bytes

Lines

1356

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/moduleparam.h
• linux/pci.h
• linux/kernel.h
• linux/delay.h
• linux/ioport.h
• linux/sched.h
• linux/slab.h
• linux/errno.h
• linux/init.h
• linux/timer.h
• linux/list.h
• linux/usb.h
• linux/usb/otg.h
• linux/usb/hcd.h
• linux/dma-mapping.h
• linux/dmapool.h
• linux/workqueue.h
• linux/debugfs.h
• linux/genalloc.h
• asm/io.h
• asm/irq.h
• linux/unaligned.h
• asm/byteorder.h
• ohci.h
• pci-quirks.h
• ohci-hub.c
• ohci-dbg.c
• ohci-mem.c
• ohci-q.c
• ohci-sa1111.c
• ohci-ppc-of.c

Detected Declarations

• function number_of_tds
• function ohci_urb_enqueue
• function queues
• function ohci_endpoint_disable
• function ohci_get_frame
• function ohci_usb_reset
• function _ohci_shutdown
• function ohci_shutdown
• function ohci_init
• function ohci_run
• function ohci_setup
• function ohci_start
• function io_watchdog_func
• function list_for_each_entry_continue
• function ohci_irq
• function ohci_stop
• function ohci_restart
• function ohci_suspend
• function ohci_resume
• function ohci_init_driver
• function ohci_hcd_mod_init
• function ohci_hcd_mod_exit
• module init ohci_hcd_mod_init
• export ohci_setup
• export ohci_restart
• export ohci_suspend
• export ohci_resume
• export ohci_init_driver

Annotated Snippet

module_init(ohci_hcd_mod_init);

static void __exit ohci_hcd_mod_exit(void)
{
#ifdef SM501_OHCI_DRIVER
	platform_driver_unregister(&SM501_OHCI_DRIVER);
#endif
#ifdef SA1111_DRIVER
	sa1111_driver_unregister(&SA1111_DRIVER);
#endif
#ifdef OF_PLATFORM_DRIVER
	platform_driver_unregister(&OF_PLATFORM_DRIVER);
#endif
#ifdef PS3_SYSTEM_BUS_DRIVER
	ps3_ohci_driver_unregister(&PS3_SYSTEM_BUS_DRIVER);
#endif
	debugfs_remove(ohci_debug_root);
}
module_exit(ohci_hcd_mod_exit);

Annotation

• Immediate include surface: `linux/module.h`, `linux/moduleparam.h`, `linux/pci.h`, `linux/kernel.h`, `linux/delay.h`, `linux/ioport.h`, `linux/sched.h`, `linux/slab.h`.
• Detected declarations: `function number_of_tds`, `function ohci_urb_enqueue`, `function queues`, `function ohci_endpoint_disable`, `function ohci_get_frame`, `function ohci_usb_reset`, `function _ohci_shutdown`, `function ohci_shutdown`, `function ohci_init`, `function ohci_run`.
• 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.