Skip to contentSkip to conversation

ACPI: CPPC: Fix some kernel-doc comments

PATCH New Yang Li 1 participant 1 message Feb 8, 2023

Subsystems (2)
lore
Share & tools
lore

Yang Li

author
#0 lore raw

PATCH 1/1 ACPI: CPPC: Fix some kernel-doc comments

Add the description of @pcc_ss_id in pcc_data_alloc(). Add the description of @cpu_num in cppc_get_transition_latency().

clear the below warnings:
drivers/acpi/cppc_acpi.c:607: warning: Function parameter or member 'pcc_ss_id' not described in 'pcc_data_alloc' drivers/acpi/cppc_acpi.c:1616: warning: Function parameter or member 'cpu_num' not described in 'cppc_get_transition_latency'

---
 drivers/acpi/cppc_acpi.c | 5 +++++
 1 file changed, 5 insertions(+)
drivers/acpi/cppc_acpi.c +5 -0
index 02d83c807271..bc7b304944a7 100644
@@ -596,6 +596,9 @@ bool __weak cpc_supported_by_cpu(void)
 /**
  * pcc_data_alloc() - Allocate the pcc_data memory for pcc subspace
  *
+ * @pcc_ss_id: The PCC Subspace index as parsed in the PCC client
+ *	       ACPI package.
+ *
  * Check and allocate the cppc_pcc_data memory.
  * In some processor configurations it is possible that same subspace
  * is shared between multiple CPUs. This is seen especially in CPUs
@@ -1604,6 +1607,8 @@ EXPORT_SYMBOL_GPL(cppc_set_perf);
 /**
  * cppc_get_transition_latency - returns frequency transition latency in ns
  *
+ * @cpu_num: the number of the specified cpu for per_cpu()
+ *
  * ACPI CPPC does not explicitly specify how a platform can specify the
  * transition latency for performance change requests. The closest we have
  * is the timing information from the PCCT tables which provides the info
Signature · 1 line
2.20.1.7.g153144c