drivers/hwtracing/intel_th/Makefile

File Facts

System

Linux kernel

Corpus path

drivers/hwtracing/intel_th/Makefile

Extension

[no extension]

Size

663 bytes

Lines

26

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
obj-$(CONFIG_INTEL_TH)		+= intel_th.o
intel_th-y			:= core.o
intel_th-$(CONFIG_INTEL_TH_DEBUG) += debug.o

obj-$(CONFIG_INTEL_TH_PCI)	+= intel_th_pci.o
intel_th_pci-y			:= pci.o

obj-$(CONFIG_INTEL_TH_ACPI)	+= intel_th_acpi.o
intel_th_acpi-y			:= acpi.o

obj-$(CONFIG_INTEL_TH_GTH)	+= intel_th_gth.o
intel_th_gth-y			:= gth.o

obj-$(CONFIG_INTEL_TH_STH)	+= intel_th_sth.o
intel_th_sth-y			:= sth.o

obj-$(CONFIG_INTEL_TH_MSU)	+= intel_th_msu.o
intel_th_msu-y			:= msu.o

obj-$(CONFIG_INTEL_TH_PTI)	+= intel_th_pti.o
intel_th_pti-y			:= pti.o

obj-$(CONFIG_INTEL_TH_MSU)	+= intel_th_msu_sink.o
intel_th_msu_sink-y		:= msu-sink.o

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.