drivers/usb/phy/phy-ab8500-usb.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/phy/phy-ab8500-usb.c

Extension

.c

Size

26401 bytes

Lines

1012

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/platform_device.h
• linux/usb/otg.h
• linux/slab.h
• linux/notifier.h
• linux/interrupt.h
• linux/delay.h
• linux/clk.h
• linux/err.h
• linux/mfd/abx500.h
• linux/mfd/abx500/ab8500.h
• linux/usb/musb-ux500.h
• linux/regulator/consumer.h
• linux/pinctrl/consumer.h

Detected Declarations

• struct ab8500_usb
• enum ab8500_usb_link_status
• enum ab8505_usb_link_status
• enum ab8500_usb_mode
• function ab8500_usb_wd_workaround
• function ab8500_usb_regulator_enable
• function ab8500_usb_regulator_disable
• function ab8500_usb_wd_linkstatus
• function ab8500_usb_phy_enable
• function ab8500_usb_phy_disable
• function ab8505_usb_link_status_update
• function ab8500_usb_link_status_update
• function abx500_usb_link_status_update
• function ab8500_usb_disconnect_irq
• function ab8500_usb_link_status_irq
• function ab8500_usb_phy_disable_work
• function ab8500_usb_set_suspend
• function ab8500_usb_set_peripheral
• function ab8500_usb_set_host
• function ab8500_usb_restart_phy
• function ab8500_usb_regulator_get
• function ab8500_usb_irq_setup
• function ab8500_usb_set_ab8500_tuning_values
• function ab8500_usb_set_ab8505_tuning_values
• function ab8500_usb_probe
• function ab8500_usb_remove
• function ab8500_usb_init
• function ab8500_usb_exit
• module init ab8500_usb_init

Annotated Snippet

subsys_initcall(ab8500_usb_init);

static void __exit ab8500_usb_exit(void)
{
	platform_driver_unregister(&ab8500_usb_driver);
}
module_exit(ab8500_usb_exit);

MODULE_AUTHOR("ST-Ericsson AB");
MODULE_DESCRIPTION("AB8500 family usb transceiver driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/platform_device.h`, `linux/usb/otg.h`, `linux/slab.h`, `linux/notifier.h`, `linux/interrupt.h`, `linux/delay.h`, `linux/clk.h`.
• Detected declarations: `struct ab8500_usb`, `enum ab8500_usb_link_status`, `enum ab8505_usb_link_status`, `enum ab8500_usb_mode`, `function ab8500_usb_wd_workaround`, `function ab8500_usb_regulator_enable`, `function ab8500_usb_regulator_disable`, `function ab8500_usb_wd_linkstatus`, `function ab8500_usb_phy_enable`, `function ab8500_usb_phy_disable`.
• 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.