drivers/usb/renesas_usbhs/Kconfig

Source file repositories/reference/linux-study-clean/drivers/usb/renesas_usbhs/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/usb/renesas_usbhs/Kconfig
Extension: [no extension]
Size: 603 bytes
Lines: 18
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
#
# Renesas USBHS Controller Drivers
#

config USB_RENESAS_USBHS
	tristate 'Renesas USBHS controller'
	depends on USB_GADGET
	depends on ARCH_RENESAS || SUPERH || COMPILE_TEST
	depends on EXTCON || !EXTCON # if EXTCON=m, USBHS cannot be built-in
	help
	  Renesas USBHS is a discrete USB host and peripheral controller chip
	  that supports both full and high speed USB 2.0 data transfers.
	  It has nine or more configurable endpoints, and endpoint zero.

	  Say "y" to link the driver statically, or "m" to build a
	  dynamically linked module called "renesas_usbhs"

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.