drivers/usb/typec/ucsi/ucsi.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/typec/ucsi/ucsi.c

Extension

.c

Size

55327 bytes

Lines

2207

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.
• 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/completion.h
• linux/property.h
• linux/device.h
• linux/module.h
• linux/delay.h
• linux/slab.h
• linux/usb/typec_dp.h
• linux/usb/typec_tbt.h
• ucsi.h
• trace.h

Detected Declarations

• struct ucsi_work
• function Copyright
• function ucsi_sync_control_common
• function ucsi_acknowledge
• function ucsi_run_command
• function ucsi_read_error
• function ucsi_send_command_common
• function ucsi_send_command
• function ucsi_poll_worker
• function ucsi_partner_task
• function ucsi_altmode_update_active
• function ucsi_altmode_next_mode
• function ucsi_next_altmode
• function ucsi_get_num_altmode
• function ucsi_register_altmode
• function ucsi_register_altmodes_nvidia
• function ucsi_register_altmodes
• function ucsi_unregister_altmodes
• function ucsi_get_connector_status
• function ucsi_read_pdos
• function ucsi_get_pdos
• function ucsi_get_src_pdos
• function ucsi_get_pd_message
• function ucsi_get_partner_identity
• function ucsi_get_cable_identity
• function ucsi_check_altmodes
• function ucsi_register_device_pdos
• function ucsi_register_partner_pdos
• function ucsi_unregister_partner_pdos
• function ucsi_register_plug
• function ucsi_unregister_plug
• function ucsi_register_cable
• function ucsi_unregister_cable
• function ucsi_check_connector_capability
• function ucsi_orientation
• function ucsi_pwr_opmode_change
• function ucsi_register_partner
• function ucsi_unregister_partner
• function ucsi_partner_change
• function ucsi_check_connection
• function ucsi_check_cable
• function ucsi_handle_connector_change
• function ucsi_connector_change
• function ucsi_reset_connector
• function ucsi_reset_ppm
• function ucsi_role_cmd
• function ucsi_dr_swap
• function ucsi_pr_swap

Annotated Snippet

module_init(ucsi_module_init);

static void __exit ucsi_module_exit(void)
{
	ucsi_debugfs_exit();
}
module_exit(ucsi_module_exit);

MODULE_AUTHOR("Heikki Krogerus <heikki.krogerus@linux.intel.com>");
MODULE_LICENSE("GPL v2");
MODULE_DESCRIPTION("USB Type-C Connector System Software Interface driver");

Annotation

• Immediate include surface: `linux/completion.h`, `linux/property.h`, `linux/device.h`, `linux/module.h`, `linux/delay.h`, `linux/slab.h`, `linux/usb/typec_dp.h`, `linux/usb/typec_tbt.h`.
• Detected declarations: `struct ucsi_work`, `function Copyright`, `function ucsi_sync_control_common`, `function ucsi_acknowledge`, `function ucsi_run_command`, `function ucsi_read_error`, `function ucsi_send_command_common`, `function ucsi_send_command`, `function ucsi_poll_worker`, `function ucsi_partner_task`.
• 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.

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.