drivers/usb/typec/altmodes/Kconfig
Source file repositories/reference/linux-study-clean/drivers/usb/typec/altmodes/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/usb/typec/altmodes/Kconfig- Extension
[no extension]- Size
- 1015 bytes
- Lines
- 36
- Domain
- Driver Families
- Bucket
- drivers/usb
- 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
menu "USB Type-C Alternate Mode drivers"
config TYPEC_DP_ALTMODE
tristate "DisplayPort Alternate Mode driver"
depends on DRM
help
DisplayPort USB Type-C Alternate Mode allows DisplayPort
displays and adapters to be attached to the USB Type-C
connectors on the system.
To compile this driver as a module, choose M here: the
module will be called typec_displayport.
config TYPEC_NVIDIA_ALTMODE
tristate "NVIDIA Alternate Mode driver"
depends on TYPEC_DP_ALTMODE
help
Latest NVIDIA GPUs support VirtualLink devices. Select this
to enable support for VirtualLink devices with NVIDIA GPUs.
To compile this driver as a module, choose M here: the
module will be called typec_nvidia.
config TYPEC_TBT_ALTMODE
tristate "Thunderbolt3 Alternate Mode driver"
help
Select this option if you have Thunderbolt3 hardware on your
system.
To compile this driver as a module, choose M here: the
module will be called typec_thunderbolt.
endmenu
Annotation
- Atlas domain: Driver Families / drivers/usb.
- 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.