include/acpi/cppc_acpi.h
Source file repositories/reference/linux-study-clean/include/acpi/cppc_acpi.h
File Facts
- System
- Linux kernel
- Corpus path
include/acpi/cppc_acpi.h- Extension
.h- Size
- 8153 bytes
- Lines
- 308
- Domain
- Repository Root And Misc
- Bucket
- include
- Inferred role
- Repository Root And Misc: implementation source
- Status
- source implementation candidate
Why This File Exists
Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/acpi.hlinux/cpufreq.hlinux/types.hacpi/pcc.hacpi/processor.h
Detected Declarations
struct cpc_regstruct cpc_register_resourcestruct cpc_descstruct cppc_perf_capsstruct cppc_perf_ctrlsstruct cppc_perf_fb_ctrsstruct cppc_cpudataenum cppc_regsfunction cppc_get_desired_perffunction cppc_get_nominal_perffunction cppc_get_highest_perffunction cppc_get_perf_ctrsfunction cppc_get_perffunction cppc_set_perffunction cppc_set_enablefunction cppc_get_perf_capsfunction cppc_perf_ctrs_in_pcc_cpufunction cppc_perf_ctrs_in_pccfunction acpi_cpc_validfunction cppc_allow_fast_switchfunction cppc_get_transition_latencyfunction cpc_ffh_supportedfunction cpc_read_ffhfunction cpc_write_ffhfunction cppc_set_epp_perffunction cppc_get_epp_perffunction cppc_set_eppfunction cppc_get_auto_act_windowfunction cppc_set_auto_act_windowfunction cppc_get_auto_selfunction cppc_set_auto_selfunction cppc_get_perf_limitedfunction cppc_set_perf_limitedfunction amd_get_highest_perffunction amd_get_boost_ratio_numeratorfunction amd_detect_prefcore
Annotated Snippet
struct cpc_reg {
u8 descriptor;
u16 length;
u8 space_id;
u8 bit_width;
u8 bit_offset;
u8 access_width;
u64 address;
} __packed;
/*
* Each entry in the CPC table is either
* of type ACPI_TYPE_BUFFER or
* ACPI_TYPE_INTEGER.
*/
struct cpc_register_resource {
acpi_object_type type;
u64 __iomem *sys_mem_vaddr;
union {
struct cpc_reg reg;
u64 int_value;
} cpc_entry;
};
/* Container to hold the CPC details for each CPU */
struct cpc_desc {
int num_entries;
int version;
int cpu_id;
int write_cmd_status;
int write_cmd_id;
/* Lock used for RMW operations in cpc_write() */
raw_spinlock_t rmw_lock;
struct cpc_register_resource cpc_regs[MAX_CPC_REG_ENT];
struct acpi_psd_package domain_info;
struct kobject kobj;
};
/* These are indexes into the per-cpu cpc_regs[]. Order is important. */
enum cppc_regs {
HIGHEST_PERF,
NOMINAL_PERF,
LOW_NON_LINEAR_PERF,
LOWEST_PERF,
GUARANTEED_PERF,
DESIRED_PERF,
MIN_PERF,
MAX_PERF,
PERF_REDUC_TOLERANCE,
TIME_WINDOW,
CTR_WRAP_TIME,
REFERENCE_CTR,
DELIVERED_CTR,
PERF_LIMITED,
ENABLE,
AUTO_SEL_ENABLE,
AUTO_ACT_WINDOW,
ENERGY_PERF,
REFERENCE_PERF,
LOWEST_FREQ,
NOMINAL_FREQ,
OSPM_NOMINAL_PERF,
RESOURCE_PRIORITY,
};
/*
* Categorization of registers as described
* in the ACPI v.5.1 spec.
* XXX: Only filling up ones which are used by governors
* today.
*/
struct cppc_perf_caps {
u32 guaranteed_perf;
u32 highest_perf;
u32 nominal_perf;
u32 reference_perf;
u32 lowest_perf;
u32 lowest_nonlinear_perf;
u32 lowest_freq;
u32 nominal_freq;
};
struct cppc_perf_ctrls {
u32 max_perf;
u32 min_perf;
u32 desired_perf;
u32 energy_perf;
bool auto_sel;
};
Annotation
- Immediate include surface: `linux/acpi.h`, `linux/cpufreq.h`, `linux/types.h`, `acpi/pcc.h`, `acpi/processor.h`.
- Detected declarations: `struct cpc_reg`, `struct cpc_register_resource`, `struct cpc_desc`, `struct cppc_perf_caps`, `struct cppc_perf_ctrls`, `struct cppc_perf_fb_ctrs`, `struct cppc_cpudata`, `enum cppc_regs`, `function cppc_get_desired_perf`, `function cppc_get_nominal_perf`.
- Atlas domain: Repository Root And Misc / include.
- 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.