cpu cpu0: dev_pm_opp_get_max_volt_latency: Invalid regulator (-6)
Hello,
I'm using next-20160428
I've enabled the generic cpufreq-dt driver.
I'm hitting this dev_err in drivers/base/power/opp/core.c
reg = opp_table->regulator;
if (IS_ERR(reg)) {
/* Regulator may not be required for device */
if (reg)
dev_err(dev, "%s: Invalid regulator (%ld)\n", __func__, PTR_ERR(reg));Apparent call stack:dev_pm_opp_get_max_volt_latency()dev_pm_opp_get_max_transition_latency()cpufreq_init()
Relevant commit655c9df961751 PM / OPP: Introduce dev_pm_opp_get_max_volt_latency()
My platform's DT
cpu0: cpu@0 {
compatible = "arm,cortex-a9";
next-level-cache = <&l2cc>;
device_type = "cpu";
reg = <0>;
clocks = <&clkgen CPU_CLK>;
clock-latency = <1>;
operating-points = <1215000 0 607500 0 405000 0 243000 0 135000 0>;
};(My platform does not support voltage scaling.)
Is this error relevant to my platform? (I don't think so.) Is there a way to mute the error on my platform?
Regards.
Quoted 6 lines · Mason
Hello,
I'm using next-20160428
I've enabled the generic cpufreq-dt driver.
Quoted 7 lines
I'm hitting this
dev_errindrivers/base/power/opp/core.creg = opp_table->regulator; if (IS_ERR(reg)) { /* Regulator may not be required for device */ if (reg) dev_err(dev, "%s: Invalid regulator (%ld)\n", __func__, PTR_ERR(reg));
This check is always going to pass and looks stupid, yeah I wrote it :)
Sent a separate patch to get it fixed.
Signature · 1 line
viresh