drivers/usb/host/octeon-hcd.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/host/octeon-hcd.c

Extension

.c

Size

112878 bytes

Lines

3738

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/usb.h
• linux/slab.h
• linux/module.h
• linux/usb/hcd.h
• linux/prefetch.h
• linux/irqdomain.h
• linux/dma-mapping.h
• linux/platform_device.h
• linux/of.h
• asm/octeon/octeon.h
• octeon-hcd.h

Detected Declarations

• struct cvmx_usb_port_status
• struct cvmx_usb_iso_packet
• struct cvmx_usb_transaction
• struct cvmx_usb_pipe
• struct cvmx_usb_tx_fifo
• struct octeon_hcd
• struct octeon_temp_buffer
• enum cvmx_usb_speed
• enum cvmx_usb_transfer
• enum cvmx_usb_direction
• enum cvmx_usb_status
• enum cvmx_usb_initialize_flags
• enum cvmx_usb_pipe_flags
• enum cvmx_usb_stage
• function octeon_alloc_temp_buffer
• function octeon_alloc_temp_buffer
• function octeon_map_urb_for_dma
• function octeon_unmap_urb_for_dma
• function cvmx_usb_read_csr32
• function cvmx_usb_write_csr32
• function cvmx_usb_pipe_needs_split
• function cvmx_usb_get_data_pid
• function cvmx_wait_tx_rx
• function cvmx_fifo_setup
• function cvmx_usb_initialize
• function cvmx_usb_initialize
• function cvmx_usb_reset_port
• function cvmx_usb_disable
• function cvmx_usb_get_status
• function cvmx_usb_poll_rx_fifo
• function cvmx_usb_fill_tx_hw
• function cvmx_usb_poll_tx_fifo
• function cvmx_usb_fill_tx_fifo
• function cvmx_usb_start_channel
• function cvmx_usb_start_channel
• function list_for_each_entry
• function cvmx_usb_schedule
• function list_for_each_entry
• function octeon_usb_urb_complete_callback
• function cvmx_usb_complete
• function cvmx_usb_poll
• function cvmx_usb_cancel
• function cvmx_usb_open_pipe
• function cvmx_usb_get_frame_number
• function cvmx_usb_transfer_control
• function cvmx_usb_transfer_bulk
• function cvmx_usb_transfer_intr
• function cvmx_usb_transfer_isoc

Annotated Snippet

module_init(octeon_usb_driver_init);

static void __exit octeon_usb_driver_exit(void)
{
	if (usb_disabled())
		return;

	platform_driver_unregister(&octeon_usb_driver);
}
module_exit(octeon_usb_driver_exit);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Cavium, Inc. <support@cavium.com>");
MODULE_DESCRIPTION("Cavium Inc. OCTEON USB Host driver.");

Annotation

• Immediate include surface: `linux/usb.h`, `linux/slab.h`, `linux/module.h`, `linux/usb/hcd.h`, `linux/prefetch.h`, `linux/irqdomain.h`, `linux/dma-mapping.h`, `linux/platform_device.h`.
• Detected declarations: `struct cvmx_usb_port_status`, `struct cvmx_usb_iso_packet`, `struct cvmx_usb_transaction`, `struct cvmx_usb_pipe`, `struct cvmx_usb_tx_fifo`, `struct octeon_hcd`, `struct octeon_temp_buffer`, `enum cvmx_usb_speed`, `enum cvmx_usb_transfer`, `enum cvmx_usb_direction`.
• 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.