drivers/phy/ti/phy-twl4030-usb.c

File Facts

System

Linux kernel

Corpus path

drivers/phy/ti/phy-twl4030-usb.c

Extension

.c

Size

22841 bytes

Lines

860

Domain

Driver Families

Bucket

drivers/phy

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/init.h
• linux/interrupt.h
• linux/of.h
• linux/platform_device.h
• linux/workqueue.h
• linux/io.h
• linux/delay.h
• linux/usb/otg.h
• linux/phy/phy.h
• linux/pm_runtime.h
• linux/usb/musb.h
• linux/usb/ulpi.h
• linux/mfd/twl.h
• linux/regulator/consumer.h
• linux/err.h
• linux/slab.h

Detected Declarations

• struct twl4030_usb
• function cable_present
• function twl4030_i2c_write_u8_verify
• function twl4030_usb_write
• function twl4030_readb
• function twl4030_usb_read
• function twl4030_usb_set_bits
• function twl4030_usb_clear_bits
• function twl4030_is_driving_vbus
• function twl4030_usb_linkstat
• function twl4030_usb_set_mode
• function twl4030_i2c_access
• function __twl4030_phy_power
• function twl4030_usb_suspend
• function twl4030_usb_resume
• function twl4030_usb_runtime_suspend
• function twl4030_usb_runtime_resume
• function twl4030_phy_power_off
• function twl4030_phy_power_on
• function twl4030_usb_ldo_init
• function vbus_show
• function twl4030_usb_irq
• function twl4030_id_workaround_work
• function twl4030_phy_init
• function twl4030_set_peripheral
• function twl4030_set_host
• function twl4030_usb_probe
• function twl4030_usb_remove
• function twl4030_usb_init
• function twl4030_usb_exit
• module init twl4030_usb_init

Annotated Snippet

subsys_initcall(twl4030_usb_init);

static void __exit twl4030_usb_exit(void)
{
	platform_driver_unregister(&twl4030_usb_driver);
}
module_exit(twl4030_usb_exit);

MODULE_ALIAS("platform:twl4030_usb");
MODULE_AUTHOR("Texas Instruments, Inc, Nokia Corporation");
MODULE_DESCRIPTION("TWL4030 USB transceiver driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/init.h`, `linux/interrupt.h`, `linux/of.h`, `linux/platform_device.h`, `linux/workqueue.h`, `linux/io.h`, `linux/delay.h`.
• Detected declarations: `struct twl4030_usb`, `function cable_present`, `function twl4030_i2c_write_u8_verify`, `function twl4030_usb_write`, `function twl4030_readb`, `function twl4030_usb_read`, `function twl4030_usb_set_bits`, `function twl4030_usb_clear_bits`, `function twl4030_is_driving_vbus`, `function twl4030_usb_linkstat`.
• Atlas domain: Driver Families / drivers/phy.
• 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.