drivers/hwtracing/ptt/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/hwtracing/ptt/Kconfig

Extension

[no extension]

Size

468 bytes

Lines

13

Domain

Driver Families

Bucket

drivers/hwtracing

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 HISI_PTT
	tristate "HiSilicon PCIe Tune and Trace Device"
	depends on ARM64 || (COMPILE_TEST && 64BIT)
	depends on PCI && HAS_DMA && HAS_IOMEM && PERF_EVENTS
	help
	  HiSilicon PCIe Tune and Trace device exists as a PCIe RCiEP
	  device, and it provides support for PCIe traffic tuning and
	  tracing TLP headers to the memory.

	  This driver can also be built as a module. If so, the module
	  will be called hisi_ptt.

Annotation

• Atlas domain: Driver Families / drivers/hwtracing.
• 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.