The operating-points-v2 binding names the per-OPP latency
"clock-latency-ns", but the parser looked for "clock-latency", so the
latency of every v2 OPP was reported as unknown.
The device tree gives the latencies in nanoseconds (this is also the
case for the "clock-latency" of operating-points v1) while the cpufreq
framework wants them in microseconds. Convert them, rounding up so a
non-zero latency never becomes 0.
Fixes: 41a76289e601 ("cpufreq_dt: Add operating-points-v2 support")
Fixes: 319336a943a5 ("Add generic device-tree cpufreq driver.")