drivers/phy/tegra/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/phy/tegra/Kconfig
Extension: [no extension]
Size: 601 bytes
Lines: 21
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
config PHY_TEGRA_XUSB
	tristate "NVIDIA Tegra XUSB pad controller driver"
	depends on ARCH_TEGRA && USB_SUPPORT
	select USB_COMMON
	select USB_CONN_GPIO
	select USB_PHY
	help
	  Choose this option if you have an NVIDIA Tegra SoC.

	  To compile this driver as a module, choose M here: the module will
	  be called phy-tegra-xusb.

config PHY_TEGRA194_P2U
	tristate "NVIDIA Tegra194 PIPE2UPHY PHY driver"
	depends on ARCH_TEGRA || COMPILE_TEST
	select GENERIC_PHY
	help
	  Enable this to support the P2U (PIPE to UPHY) that is part of Tegra 19x
	  and 234 SOCs.

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.