drivers/usb/misc/uss720.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/misc/uss720.c

Extension

.c

Size

22891 bytes

Lines

836

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/socket.h
• linux/parport.h
• linux/init.h
• linux/usb.h
• linux/delay.h
• linux/completion.h
• linux/kref.h
• linux/slab.h
• linux/sched/signal.h

Detected Declarations

• struct parport_uss720_private
• struct uss720_async_request
• function destroy_priv
• function destroy_async
• function async_complete
• function kill_all_async_requests_priv
• function get_1284_register
• function set_1284_register
• function change_mode
• function clear_epp_timeout
• function uss720_irq
• function parport_uss720_write_data
• function parport_uss720_read_data
• function parport_uss720_write_control
• function parport_uss720_read_control
• function parport_uss720_frob_control
• function parport_uss720_read_status
• function parport_uss720_disable_irq
• function parport_uss720_enable_irq
• function parport_uss720_data_forward
• function parport_uss720_data_reverse
• function parport_uss720_init_state
• function parport_uss720_save_state
• function parport_uss720_restore_state
• function parport_uss720_epp_read_data
• function parport_uss720_epp_write_data
• function parport_uss720_epp_read_addr
• function parport_uss720_epp_write_addr
• function parport_uss720_ecp_write_data
• function parport_uss720_ecp_read_data
• function parport_uss720_ecp_write_addr
• function parport_uss720_write_compat
• function uss720_probe
• function uss720_disconnect
• function uss720_init
• function uss720_cleanup
• module init uss720_init

Annotated Snippet

module_init(uss720_init);
module_exit(uss720_cleanup);

/* --------------------------------------------------------------------- */

Annotation

• Immediate include surface: `linux/module.h`, `linux/socket.h`, `linux/parport.h`, `linux/init.h`, `linux/usb.h`, `linux/delay.h`, `linux/completion.h`, `linux/kref.h`.
• Detected declarations: `struct parport_uss720_private`, `struct uss720_async_request`, `function destroy_priv`, `function destroy_async`, `function async_complete`, `function kill_all_async_requests_priv`, `function get_1284_register`, `function set_1284_register`, `function change_mode`, `function clear_epp_timeout`.
• 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.