drivers/phy/ti/phy-omap-control.c

File Facts

System

Linux kernel

Corpus path

drivers/phy/ti/phy-omap-control.c

Extension

.c

Size

8884 bytes

Lines

340

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.
• 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/platform_device.h
• linux/property.h
• linux/slab.h
• linux/of.h
• linux/err.h
• linux/io.h
• linux/clk.h
• linux/phy/omap_control_phy.h

Detected Declarations

• function Copyright
• function omap_control_phy_power
• function omap_control_usb_host_mode
• function omap_control_usb_device_mode
• function omap_control_usb_set_sessionend
• function omap_control_usb_set_mode
• function omap_control_phy_probe
• function omap_control_phy_init
• function omap_control_phy_exit
• module init omap_control_phy_init
• export omap_control_pcie_pcs
• export omap_control_phy_power
• export omap_control_usb_set_mode

Annotated Snippet

subsys_initcall(omap_control_phy_init);

static void __exit omap_control_phy_exit(void)
{
	platform_driver_unregister(&omap_control_phy_driver);
}
module_exit(omap_control_phy_exit);

MODULE_AUTHOR("Texas Instruments Inc.");
MODULE_DESCRIPTION("OMAP Control Module PHY Driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/module.h`, `linux/platform_device.h`, `linux/property.h`, `linux/slab.h`, `linux/of.h`, `linux/err.h`, `linux/io.h`, `linux/clk.h`.
• Detected declarations: `function Copyright`, `function omap_control_phy_power`, `function omap_control_usb_host_mode`, `function omap_control_usb_device_mode`, `function omap_control_usb_set_sessionend`, `function omap_control_usb_set_mode`, `function omap_control_phy_probe`, `function omap_control_phy_init`, `function omap_control_phy_exit`, `module init omap_control_phy_init`.
• Atlas domain: Driver Families / drivers/phy.
• Implementation status: integration implementation candidate.

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.