drivers/usb/gadget/udc/goku_udc.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/gadget/udc/goku_udc.c

Extension

.c

Size

46364 bytes

Lines

1861

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.
• 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/kernel.h
• linux/module.h
• linux/pci.h
• linux/delay.h
• linux/ioport.h
• linux/slab.h
• linux/errno.h
• linux/timer.h
• linux/list.h
• linux/interrupt.h
• linux/proc_fs.h
• linux/seq_file.h
• linux/device.h
• linux/usb/ch9.h
• linux/usb/gadget.h
• linux/prefetch.h
• asm/byteorder.h
• asm/io.h
• asm/irq.h
• linux/unaligned.h
• goku_udc.h

Detected Declarations

• function command
• function goku_ep_enable
• function ep_reset
• function goku_ep_disable
• function goku_alloc_request
• function goku_free_request
• function done
• function write_packet
• function write_fifo
• function read_fifo
• function pio_irq_enable
• function pio_irq_disable
• function pio_advance
• function start_dma
• function dma_advance
• function abort_dma
• function goku_queue
• function nuke
• function goku_dequeue
• function goku_clear_halt
• function goku_set_halt
• function goku_fifo_status
• function goku_fifo_flush
• function goku_get_frame
• function dump_intmask
• function udc_proc_read
• function list_for_each_entry
• function udc_reinit
• function udc_reset
• function ep0_start
• function udc_enable
• function set_configuration
• function stop_activity
• function goku_udc_stop
• function ep0_setup
• function goku_irq
• function gadget_release
• function goku_remove
• function goku_probe

Annotated Snippet

static struct pci_driver goku_pci_driver = {
	.name =		driver_name,
	.id_table =	pci_ids,

	.probe =	goku_probe,
	.remove =	goku_remove,

	/* FIXME add power management support */
};

module_pci_driver(goku_pci_driver);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/pci.h`, `linux/delay.h`, `linux/ioport.h`, `linux/slab.h`, `linux/errno.h`, `linux/timer.h`.
• Detected declarations: `function command`, `function goku_ep_enable`, `function ep_reset`, `function goku_ep_disable`, `function goku_alloc_request`, `function goku_free_request`, `function done`, `function write_packet`, `function write_fifo`, `function read_fifo`.
• Atlas domain: Driver Families / drivers/usb.
• Implementation status: pattern 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.