drivers/phy/motorola/Kconfig

Source file repositories/reference/linux-study-clean/drivers/phy/motorola/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/phy/motorola/Kconfig
Extension: [no extension]
Size: 589 bytes
Lines: 22
Domain: Driver Families
Bucket: drivers/phy
Inferred role: Driver Families: build/configuration rule
Status: atlas-only

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.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-only
#
# Phy drivers for Motorola devices
#
config PHY_CPCAP_USB
	tristate "CPCAP PMIC USB PHY driver"
	depends on USB_SUPPORT && IIO
	depends on USB_MUSB_HDRC || USB_MUSB_HDRC=n
	select GENERIC_PHY
	select USB_PHY
	help
	  Enable this for USB to work on Motorola phones and tablets
	  such as Droid 4.

config PHY_MAPPHONE_MDM6600
	tristate "Motorola Mapphone MDM6600 modem USB PHY driver"
	depends on OF && USB_SUPPORT && GPIOLIB
	select GENERIC_PHY
	help
	  Enable this for MDM6600 USB modem to work on Motorola phones
	  and tablets such as Droid 4.

Annotation

Atlas domain: Driver Families / drivers/phy.
Implementation status: atlas-only.

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.