drivers/platform/x86/intel_ips.c

File Facts

System

Linux kernel

Corpus path

drivers/platform/x86/intel_ips.c

Extension

.c

Size

42806 bytes

Lines

1625

Domain

Driver Families

Bucket

drivers/platform

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/debugfs.h
• linux/delay.h
• linux/interrupt.h
• linux/kernel.h
• linux/kthread.h
• linux/module.h
• linux/pci.h
• linux/sched.h
• linux/sched/loadavg.h
• linux/seq_file.h
• linux/string.h
• linux/tick.h
• linux/timer.h
• linux/dmi.h
• drm/intel/i915_drm.h
• asm/msr.h
• asm/processor.h
• asm/cpu_device_id.h
• intel_ips.h
• linux/io-64-nonatomic-lo-hi.h

Detected Declarations

• struct ips_mcp_limits
• struct ips_driver
• function ips_cpu_busy
• function upwards
• function allow
• function on_each_cpu
• function ips_enable_cpu_turbo
• function on_each_cpu
• function ips_disable_cpu_turbo
• function ips_gpu_busy
• function ips_gpu_raise
• function ips_gpu_lower
• function ips_enable_gpu_turbo
• function ips_disable_gpu_turbo
• function mcp_exceeded
• function cpu_exceeded
• function mch_exceeded
• function verify_limits
• function updates
• function ips_adjust
• function calc_avg_temp
• function read_mgtv
• function read_ptv
• function read_ctv
• function get_cpu_power
• function update_average_temp
• function update_average_power
• function calc_avg_power
• function monitor_timeout
• function ips_monitor
• function ips_irq_handler
• function ips_debugfs_init
• function ips_debugfs_cleanup
• function cpu_temp_show
• function cpu_power_show
• function cpu_clamp_show
• function mch_temp_show
• function mch_power_show
• function ips_debugfs_cleanup
• function ips_debugfs_init
• function ips_get_i915_syms
• function ips_gpu_turbo_enabled
• function ips_link_to_i915_driver
• function ips_blacklist_callback
• function ips_probe
• function ips_remove
• export ips_link_to_i915_driver

Annotated Snippet

static struct pci_driver ips_pci_driver = {
	.name = "intel ips",
	.id_table = ips_id_table,
	.probe = ips_probe,
	.remove = ips_remove,
};

module_pci_driver(ips_pci_driver);

MODULE_LICENSE("GPL v2");
MODULE_AUTHOR("Jesse Barnes <jbarnes@virtuousgeek.org>");
MODULE_DESCRIPTION("Intelligent Power Sharing Driver");

Annotation

• Immediate include surface: `linux/debugfs.h`, `linux/delay.h`, `linux/interrupt.h`, `linux/kernel.h`, `linux/kthread.h`, `linux/module.h`, `linux/pci.h`, `linux/sched.h`.
• Detected declarations: `struct ips_mcp_limits`, `struct ips_driver`, `function ips_cpu_busy`, `function upwards`, `function allow`, `function on_each_cpu`, `function ips_enable_cpu_turbo`, `function on_each_cpu`, `function ips_disable_cpu_turbo`, `function ips_gpu_busy`.
• Atlas domain: Driver Families / drivers/platform.
• Implementation status: pattern implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.