drivers/extcon/extcon-usbc-tusb320.c

File Facts

System

Linux kernel

Corpus path

drivers/extcon/extcon-usbc-tusb320.c

Extension

.c

Size

16479 bytes

Lines

624

Domain

Driver Families

Bucket

drivers/extcon

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.
• 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/bitfield.h
• linux/extcon-provider.h
• linux/i2c.h
• linux/init.h
• linux/interrupt.h
• linux/kernel.h
• linux/module.h
• linux/regmap.h
• linux/usb/typec.h
• linux/usb/typec_altmode.h
• linux/usb/role.h
• linux/irq.h

Detected Declarations

• struct tusb320_priv
• struct tusb320_ops
• struct tusb320_priv
• enum tusb320_attached_state
• enum tusb320_mode
• function tusb320_check_signature
• function tusb320_set_mode
• function tusb320l_set_mode
• function tusb320_reset
• function tusb320l_get_revision
• function tusb320_set_adv_pwr_mode
• function tusb320_port_type_set
• function tusb320_extcon_irq_handler
• function tusb320_typec_irq_handler
• function tusb320_state_update_handler
• function tusb320_irq_handler
• function tusb320_extcon_probe
• function tusb320_typec_probe
• function tusb320_typec_remove
• function tusb320_probe
• function tusb320_remove
• function tusb320_init
• function tusb320_exit
• module init tusb320_init

Annotated Snippet

subsys_initcall(tusb320_init);

static void __exit tusb320_exit(void)
{
	i2c_del_driver(&tusb320_extcon_driver);
}
module_exit(tusb320_exit);

MODULE_AUTHOR("Michael Auchter <michael.auchter@ni.com>");
MODULE_DESCRIPTION("TI TUSB320 extcon driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/bitfield.h`, `linux/extcon-provider.h`, `linux/i2c.h`, `linux/init.h`, `linux/interrupt.h`, `linux/kernel.h`, `linux/module.h`, `linux/regmap.h`.
• Detected declarations: `struct tusb320_priv`, `struct tusb320_ops`, `struct tusb320_priv`, `enum tusb320_attached_state`, `enum tusb320_mode`, `function tusb320_check_signature`, `function tusb320_set_mode`, `function tusb320l_set_mode`, `function tusb320_reset`, `function tusb320l_get_revision`.
• Atlas domain: Driver Families / drivers/extcon.
• Implementation status: integration implementation candidate.
• 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.