| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 28,509
» Latest member: meabrar
» Forum threads: 15,844
» Forum posts: 115,308
Full Statistics
|
| Latest Threads |
How boot Alpine Linux
Forum: General Discussion on PinePhone
Last Post: realroot
Today, 05:26 AM
» Replies: 3
» Views: 203
|
Battery Life- hardware ab...
Forum: PinePhone Hardware
Last Post: Kevin Kofler
Today, 04:04 AM
» Replies: 1
» Views: 48
|
bookworm vs trixie discus...
Forum: Mobian on PinePhone
Last Post: zetabeta
Today, 12:04 AM
» Replies: 34
» Views: 6,406
|
2G, 3G still is in phone.
Forum: General Discussion on PinePhone
Last Post: jennybaso
Yesterday, 03:49 AM
» Replies: 5
» Views: 669
|
Pinetab 2 Not Powering On...
Forum: General
Last Post: FortranTraffic
09-18-2024, 04:27 PM
» Replies: 0
» Views: 43
|
Need Help Choosing the Ri...
Forum: General
Last Post: jacoballen
09-18-2024, 06:13 AM
» Replies: 0
» Views: 64
|
PinePhone Pro EDL boot by...
Forum: PinePhone Pro Hardware
Last Post: biketool
09-18-2024, 04:59 AM
» Replies: 3
» Views: 875
|
SailfishOS on PT2: flashi...
Forum: PineTab Software
Last Post: schuster2
09-18-2024, 02:44 AM
» Replies: 2
» Views: 618
|
The program doesn`t detec...
Forum: Mobian on PinePhone
Last Post: Kevin Kofler
09-17-2024, 03:45 PM
» Replies: 6
» Views: 1,160
|
Danctnix Linux still main...
Forum: General Discussion on PineTab
Last Post: zetabeta
09-17-2024, 12:54 PM
» Replies: 9
» Views: 1,336
|
|
|
| The RK3399 Overclock/Undervolt/Voltages Thread |
|
Posted by: generaleramon - 03-27-2021, 02:14 AM - Forum: General Discussion on Pinebook Pro
- Replies (36)
|
 |
hey, i'm tweaking the SoC voltages in the .dtsi files and i was wondering what was the lowest possible voltage that i could set for the CPU and/or GPU. Looking in the rk3399-pinebook-pro.dts i've found something that might help.
Code: vdd_cpu_l: DCDC_REG2 {
regulator-name = "vdd_cpu_l"; <<< cpu_l is the little cluster
regulator-always-on;
regulator-boot-on;
regulator-min-microvolt = <750000>; <<<750 mv
regulator-max-microvolt = <1350000>; <<<1350mv
regulator-ramp-delay = <6001>;
vdd_cpu_b: regulator@40 {
compatible = "silergy,syr827";
reg = <0x40>;
fcs,suspend-voltage-selector = <1>;
pinctrl-names = "default";
pinctrl-0 = <&vsel1_pin>;
regulator-name = "vdd_cpu_b"; <<<cpu_b is the big cluster
regulator-always-on;
regulator-boot-on;
regulator-min-microvolt = <712500>; <<<712.5 mv
regulator-max-microvolt = <1500000>; <<<1500mv
regulator-ramp-delay = <1000>;
vin-supply = <&vcc_1v8>;
vdd_gpu: regulator@41 {
compatible = "silergy,syr828";
reg = <0x41>;
fcs,suspend-voltage-selector = <1>;
pinctrl-names = "default";
pinctrl-0 = <&vsel2_pin>;
regulator-name = "vdd_gpu"; <<<GPU
regulator-always-on;
regulator-boot-on;
regulator-min-microvolt = <712500>; <<<712.5mv
regulator-max-microvolt = <1500000>; <<<1500mv
regulator-ramp-delay = <1000>;
vin-supply = <&vcc_1v8>;
###
As of now i've found that the GPU can run at 712.5mv@400Mhz no problem but i need 775mv@500Mhz so i can confirm that it can go below the stock 800mv.
Same with the 2 cpu clusters, in some cases i was able to undervolt around 200mv at the same frequency.
i'm currently running 4xA53@1.7Ghz/2xA72@2.1Ghz/GPU@1050Mhz.
<< my (old) voltage curve
###
I wonder is someone can confirm that 750-712mv is the lowest voltage that can be set and i also wonder what is the "step size", meaning how precisely i can tune it. 6.25mv like in modern gpus? 12.5? 25mv?
###
EDIT: I'm pretty sure that a 12.5mv step is accepted. The A72 Cluster is stable @1Ghz with 775mv, can't even boot with 750mv, Linpack unstable with 762.5mv.
###
EDIT2: 08/06/2021 - Here is my latest 99% stable rk3399-opp.dtsi file:
Code: cluster0_opp: opp-table0 {
compatible = "operating-points-v2";
opp-shared;
opp00 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <750000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <696000000>;
opp-microvolt = <750000>;
};
opp02 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <800000>;
};
opp03 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <850000>;
};
opp04 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <925000>;
};
opp05 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <1025000>;
};
opp06 {
opp-hz = /bits/ 64 <1512000000>;
opp-microvolt = <1075000>;
};
opp07 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1125000>;
};
opp08 {
opp-hz = /bits/ 64 <1704000000>;
opp-microvolt = <1225000>;
};
};
cluster1_opp: opp-table1 {
compatible = "operating-points-v2";
opp-shared;
opp00 {
opp-hz = /bits/ 64 <408000000>;
opp-microvolt = <725000>;
clock-latency-ns = <40000>;
};
opp01 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <750000>;
};
opp02 {
opp-hz = /bits/ 64 <696000000>;
opp-microvolt = <775000>;
};
opp03 {
opp-hz = /bits/ 64 <816000000>;
opp-microvolt = <775000>;
};
opp04 {
opp-hz = /bits/ 64 <1008000000>;
opp-microvolt = <800000>;
};
opp05 {
opp-hz = /bits/ 64 <1200000000>;
opp-microvolt = <850000>;
};
opp06 {
opp-hz = /bits/ 64 <1416000000>;
opp-microvolt = <950000>;
};
opp07 {
opp-hz = /bits/ 64 <1512000000>;
opp-microvolt = <975000>;
};
opp08 {
opp-hz = /bits/ 64 <1608000000>;
opp-microvolt = <1025000>;
};
opp09 {
opp-hz = /bits/ 64 <1704000000>;
opp-microvolt = <1075000>;
};
opp10 {
opp-hz = /bits/ 64 <1800000000>;
opp-microvolt = <1125000>;
};
opp11 {
opp-hz = /bits/ 64 <2016000000>;
opp-microvolt = <1212500>;
};
opp12 {
opp-hz = /bits/ 64 <2040000000>;
opp-microvolt = <1225000>;
};
opp13 {
opp-hz = /bits/ 64 <2088000000>;
opp-microvolt = <1250000>;
};
opp14 {
opp-hz = /bits/ 64 <2184000000>;
opp-microvolt = <1325000>;
};
opp15 {
opp-hz = /bits/ 64 <2208000000>;
opp-microvolt = <1362500>;
};
};
gpu_opp_table: opp-table2 {
compatible = "operating-points-v2";
opp00 {
opp-hz = /bits/ 64 <297000000>;
opp-microvolt = <712500>;
};
opp01 {
opp-hz = /bits/ 64 <400000000>;
opp-microvolt = <725000>;
};
opp02 {
opp-hz = /bits/ 64 <500000000>;
opp-microvolt = <787500>;
};
opp03 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <850000>;
};
opp04 {
opp-hz = /bits/ 64 <800000000>;
opp-microvolt = <1012500>;
};
opp05 {
opp-hz = /bits/ 64 <900000000>;
opp-microvolt = <1087500>;
};
opp06 {
opp-hz = /bits/ 64 <1000000000>;
opp-microvolt = <1212500>;
};
opp07 {
opp-hz = /bits/ 64 <1100000000>;
opp-microvolt = <1275000>;
};
};
};
|
|
|
|
| Complain about all the PINE 64 "issues here" - let's have a bit of fun /snark |
|
Posted by: dgdimick - 03-27-2021, 12:54 AM - Forum: General
- No Replies
|
 |
This thread is not started, supported, and probably even read by anyone from the PINE64 "management", however, here's a place we can all bitch and complain about all things PINE64. Post don't have to be realistic, are able to be solved by any human being.
I'll start with:
Why are PIN64 products not available on Amazon Prime? Everyone and their brother has their stuff on Amazon Prime, why can't the PINE64 folks do the same? I'm sure if I was running production I could get PINE64 products on Amazon Prime in less then 3 weeks.
NOTE: If the admins delete this thread, I'm not going to be upset, since it was created in the same vane as an April Fools joke.
Cheer's and just hurry up and wait for PINE64 XXX to get to you, the wait is worth it. 
|
|
|
|
| Stress testing CPU (temperature vs freq) |
|
Posted by: ashleymills - 03-26-2021, 09:35 AM - Forum: BSD on RockPro64
- No Replies
|
|
I want to understand how the CPU temperature responds to frequency changes of the big.little architecture.
This depends on the environment and cooling system. In this case the rockpro64 was enclosed in the official NAS case (with two 3.5" HDD inside) and has the tall heatsink but no other cooling (case fan not operating).
What I want to establish is how much I need to throttle the CPU in order to maintain a reasonable temperature rise.
I was aiming to test the cartesian product of all possible frequencies, but the first few results contain enough information to move to the next experiment.
I varied the big freq and little freq and ran:
for each combination. Between each stress-test there was a break of 300 seconds. Unfortunately this wasn't enough to get the temperature to drop back to its resting value, so the mean temperature results were useless, but the temperature rise contains interesting information.
Here is the table:
![[Image: stress_test.png]](https://imghost.org/images/2021/03/26/stress_test.png)
A few things can be gleaned from this information: the big CPU has a much bigger impact on temperature rise than the small CPU (at the high end): reducing the little CPU by 216mhz reduced the temperature rise by 2.5C, a reduction of 0.0116C per mhz. Reducing the big CPU by 192mhz reduced the temperature rise by 7.4C, or 0.0378C per mhz. That's a factor of ~3 so that's pretty useful to know.
Obviously don't read too much into this, I'm not going to go overboard with designing these experiments, I'm just trying to get some rough information at the present time. I don't know what the steady-state temperatures are for these combos with my setup as I only stressed the CPU for 5 minutes.
If you burn all the CPUs with the stress tool on max freq, the temperature just keeps rising and rising with the passive cooling system I have setup. I let it get to about 85C before terminating that idea. If I'm reading the spec sheet for the RK3399 correctly, the maximum temperature the chip can tolerate is 125C but I guess we don't want to let it get to that point.
What I'd like to understand next is how hard can I push the system with passive cooling that results in a steady state temperature that isn't insane. This would be useful for designing a throttling strategy in the absence of ACPI driven throttling. Then I'll look at adding a fan.
|
|
|
|
| pinephone 2 specs discussion - 5G WiFi6 BT5 NFC? - |
|
Posted by: mitcoes - 03-26-2021, 03:37 AM - Forum: General Discussion on PinePhone
- Replies (17)
|
|
Will we have a pinephone 2 specs discussion?
I would like a 5G + WiFi6 + NFC + BT5 model, even if the rest is the same as the 1
And if it has socket/s for RAM and ROM to add more RAM/ROM or change them to higher capacity or replace them if damaged or plug the ROM in other device if phone fails if some information was not backed up even better.
|
|
|
|
| Why use x000 mAh instead of x Ah in battery specs? Why no use Coulombs, (SI)? |
|
Posted by: mitcoes - 03-26-2021, 03:29 AM - Forum: General Discussion on PinePhone
- No Replies
|
|
Why use x000 mAh instead of x Ah in battery specs? Why no use Coulombs, (SI)?
I understand it is what market does, but aren't we a "nerd" community.
Al least instead of writing 3000 mAh write 3 Ah for the Pine phone battery
And even better 3 Ah / 10800 C.
Even from a marketing point of view 10800 C is perceived as more than 3000 mAh or 3 Ah even it is the same.
And I would use kC as 10.8 kC for this case.
|
|
|
|
| Kdenlive or other video editing software?? |
|
Posted by: SuttonWillow - 03-26-2021, 03:16 AM - Forum: General Discussion on Pinebook Pro
- Replies (4)
|
|
I'm tempted to get a PineBook Pro once the new batch goes up for sale and I'm curious, can the PineBook Pro do some light video editing? I'll be coming over from a ThinkPad X220 and on that machine I'd sometimes do some light editing, stuff like putting a few video clips together and maybe adding some light effects all while using proxy clips in Kdenlive. Is the Pinebook Pro capable of doing that? If not it's not a deal breaker I'm just curious essay writer
|
|
|
|
| Difficulty making calls |
|
Posted by: Zebulon Walton - 03-25-2021, 07:50 PM - Forum: Mobian on PinePhone
- Replies (10)
|
 |
Has anyone else noticed difficulty in making calls? It seems that making calls has become less reliable. (Not sure when this started happening because I'm still using the Pinephone for test purposes and don't call out with it frequently.)
What happens is that when using the dial pad, the phone just gives a brief click but the call screen with the red hangup button never comes up. Sometimes you can see it become visible for a fraction of a second before disappearing to be replaced with the keypad. Immediately repeating the call, sometimes there is brief audio from other end indicating a connection was made but the audio cuts out immediately.
Initiating calls from the contact list seems to work a little better, but it's still necessary to press the call button several times before the call screen and audio come up.
Mobian is up to the current patch level as of this writing.
|
|
|
|
|
