drivers/hwtracing/intel_th/pci.c

File Facts

System

Linux kernel

Corpus path

drivers/hwtracing/intel_th/pci.c

Extension

.c

Size

7081 bytes

Lines

210

Domain

Driver Families

Bucket

drivers/hwtracing

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern implementation candidate

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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h
• linux/module.h
• linux/device.h
• linux/sysfs.h
• linux/pci.h
• intel_th.h
• pci_ids.h

Detected Declarations

• function intel_th_pci_activate
• function intel_th_pci_deactivate
• function intel_th_pci_probe
• function intel_th_pci_remove

Annotated Snippet

static struct pci_driver intel_th_pci_driver = {
	.name		= DRIVER_NAME,
	.id_table	= intel_th_pci_id_table,
	.probe		= intel_th_pci_probe,
	.remove		= intel_th_pci_remove,
};

module_pci_driver(intel_th_pci_driver);

MODULE_LICENSE("GPL v2");
MODULE_DESCRIPTION("Intel(R) Trace Hub PCI controller driver");
MODULE_AUTHOR("Alexander Shishkin <alexander.shishkin@intel.com>");

Annotation

• Immediate include surface: `linux/types.h`, `linux/module.h`, `linux/device.h`, `linux/sysfs.h`, `linux/pci.h`, `intel_th.h`, `pci_ids.h`.
• Detected declarations: `function intel_th_pci_activate`, `function intel_th_pci_deactivate`, `function intel_th_pci_probe`, `function intel_th_pci_remove`.
• Atlas domain: Driver Families / drivers/hwtracing.
• Implementation status: pattern implementation candidate.

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.