Comment 0 for bug 1746174

== Comment: #0 - Shilpasri G. Bhat
+++ This bug was initially created as a clone of Bug #163527 +++

---Problem Description---
Error in CPU frequency reporting when nominal and min pstates are same

The patch for this issue is accepted to linux-next as

3fa4680b860bf48b437d6a2c039789c4abe202ae
cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin

Some OpenPOWER boxes can have same pstate values for nominal and
pmin pstates. In these boxes the current code will not initialize
'powernv_pstate_info.min' variable and result in erroneous CPU
frequency reporting. This patch fixes this problem.

Fixes: 09ca4c9b5958 (cpufreq: powernv: Replacing pstate_id with frequency table index)
Reported-by: Alvin Wang <email address hidden>
Signed-off-by: Shilpasri G Bhat <email address hidden>
Acked-by: Viresh Kumar <email address hidden>
Cc: 4.8+ <email address hidden> # 4.8+
Signed-off-by: Rafael J. Wysocki <email address hidden>

https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/drivers/cpufreq/powernv-cpufreq.c?h=linux-next&id=3fa4680b860bf48b437d6a2c039789c4abe202ae