Age | Commit message (Collapse) | Author |
|
|
|
from copyright holders - see: https://github.com/lpereira/hardinfo/issues/530 https://github.com/lpereira/hardinfo/issues/707
|
|
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
|
|
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
I don't have any hardware to test, this is based only on the
OPP kernel docs.
https://www.kernel.org/doc/Documentation/devicetree/bindings/opp/opp.txt
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
* opp-v2 = operating-points-v2, frequency scaling information
from device tree that can be used for cpu, gpu, etc.
* adds helper function to get the opp-v2 range of frequencies
for a node, dtr_get_opp_range() in dt_util.c
* adds a freq range in opp-v2 property for a node in dt
* reports a gpu's max clock frequency if avaiable via opp-v2
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Now that they are working better.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|