On 8 December 2016 at 19:57, Shawn Guo shawnguo@kernel.org wrote:
That's the same case when Performance governor is selected, and should be guaranteed safe, shouldn't it?
Depends on platform I would say. For example for a big LITTLE platform, running the big core on max not only increases the amount of power it uses but also the amount of heat it generates, which is really scary.
Performance governor is fine for testing but it is not used for battery operated devices in production code.
We will surely overheat most of the SoCs and burn them out.
IMO, the problem is on OPP table. Every entry in the table should be safe for running for any time.
Not necessarily. The highest OPPs might be suggested to run only for small period of time only. And there is nothing wrong in it.
Over that if some of the OPPs fail to get registered from the OPP table in DT, it surely hints at some sort of bugs in the code or DT.
Why should we try to go ahead if only a part of the DT table gets registered? I don't find a compelling reason for that. It will never happen normally anyway, as we wouldn't have any errors.
-- viresh