include/linux/pci-bwctrl.h
Source file repositories/reference/linux-study-clean/include/linux/pci-bwctrl.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/pci-bwctrl.h- Extension
.h- Size
- 650 bytes
- Lines
- 29
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/pci.h
Detected Declarations
struct thermal_cooling_devicefunction pcie_cooling_device_unregister
Annotated Snippet
#ifndef LINUX_PCI_BWCTRL_H
#define LINUX_PCI_BWCTRL_H
#include <linux/pci.h>
struct thermal_cooling_device;
#ifdef CONFIG_PCIE_THERMAL
struct thermal_cooling_device *pcie_cooling_device_register(struct pci_dev *port);
void pcie_cooling_device_unregister(struct thermal_cooling_device *cdev);
#else
static inline struct thermal_cooling_device *pcie_cooling_device_register(struct pci_dev *port)
{
return NULL;
}
static inline void pcie_cooling_device_unregister(struct thermal_cooling_device *cdev)
{
}
#endif
#endif
Annotation
- Immediate include surface: `linux/pci.h`.
- Detected declarations: `struct thermal_cooling_device`, `function pcie_cooling_device_unregister`.
- Atlas domain: Core OS / Core Kernel Interface.
- Implementation status: source 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.