On my pc2 I am using a dtb from Armbian that has operating points, but I am not
sure if sxiccmu uses it.
Maybe Mark could comment.
It is interesting to note that Armbian sets the voltage to 1.3v at 816Mhz,
whereas Openbsd starts up at 816Mhz and 1.2v.
from Armbian dtb:
opp_table0 {
compatible = "operating-points-v2";
opp-shared;
phandle = < 0x30 >;
opp@120000000 {
opp-hz = < 0x00 0x7270e00 >;
opp-microvolt = < 0xfde80 0xfde80 0x13d620 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@240000000 {
opp-hz = < 0x00 0xe4e1c00 >;
opp-microvolt = < 0xfde80 0xfde80 0x13d620 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@480000000 {
opp-hz = < 0x00 0x1c9c3800 >;
opp-microvolt = < 0xfde80 0xfde80 0x13d620 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@648000000 {
opp-hz = < 0x00 0x269fb200 >;
opp-microvolt = < 0xfde80 0xfde80 0x13d620 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@816000000 {
opp-hz = < 0x00 0x30a32c00 >;
opp-microvolt = < 0x10c8e0 0x10c8e0 0x13d620 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@960000000 {
opp-hz = < 0x00 0x39387000 >;
opp-microvolt = < 0x124f80 0x124f80 0x13d620 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@1008000000 {
opp-hz = < 0x00 0x3c14dc00 >;
opp-microvolt = < 0x124f80 0x124f80 0x13d620 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@1056000000 {
opp-hz = < 0x00 0x3ef14800 >;
opp-microvolt = < 0x142440 0x142440 0x142440 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@1104000000 {
opp-hz = < 0x00 0x41cdb400 >;
opp-microvolt = < 0x142440 0x142440 0x142440 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@1152000000 {
opp-hz = < 0x00 0x44aa2000 >;
opp-microvolt = < 0x142440 0x142440 0x142440 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@1200000000 {
opp-hz = < 0x00 0x47868c00 >;
opp-microvolt = < 0x142440 0x142440 0x142440 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@1224000000 {
opp-hz = < 0x00 0x48f4c200 >;
opp-microvolt = < 0x147260 0x147260 0x147260 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@1248000000 {
opp-hz = < 0x00 0x4a62f800 >;
opp-microvolt = < 0x147260 0x147260 0x147260 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@1296000000 {
opp-hz = < 0x00 0x4d3f6400 >;
opp-microvolt = < 0x147260 0x147260 0x147260 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@1344000000 {
opp-hz = < 0x00 0x501bd000 >;
opp-microvolt = < 0x155cc0 0x155cc0 0x155cc0 >;
clock-latency-ns = < 0x3b9b0 >;
};
opp@1368000000 {
opp-hz = < 0x00 0x518a0600 >;
opp-microvolt = < 0x155cc0 0x155cc0 0x155cc0 >;
clock-latency-ns = < 0x3b9b0 >;
};
};
cpu@0 {
compatible = "arm,cortex-a53\0arm,armv8";
device_type = "cpu";
reg = < 0x00 >;
enable-method = "psci";
clocks = < 0x03 0x0e >;
clock-names = "cpu";
operating-points-v2 = < 0x30 >;
#cooling-cells = < 0x02 >;
cooling-min-level = < 0x00 >;
cooling-max-level = < 0x0f >;
cpu-supply = < 0x31 >;
phandle = < 0x2b >;
};
From: Krystian Lewandowski <k.lewandow...@icloud.com>
Sent: February 2, 2019 12:44 PM
To: s_g...@telus.net
Cc: arm@openbsd.org
Subject: Re: initial cpu speed on orangepi one and orangepi pc2 - probably
other H5 and H3 boards
Wiadomość napisana przez s_g...@telus.net <mailto:s_g...@telus.net> w dniu
02.02.2019, o godz. 21:30:
-----Original Message-----
From: s_g...@telus.net <mailto:s_g...@telus.net> <s_g...@telus.net
<mailto:s_g...@telus.net> >
Sent: February 2, 2019 11:29 AM
To: 'Krystian Lewandowski' <k.lewandow...@icloud.com
<mailto:k.lewandow...@icloud.com> >
Subject: RE: initial cpu speed on orangepi one and orangepi pc2 - probably
other H5 and H3 boards
Thank you for your reply.
The stock dtbs do not have the "operating-points-v2" and it follows that there
is no frequency set by the dtb.
Can you point me to a dtb block that has the property with an example of
setting the frequency.
Maybe this one?
https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/sun8i-h3.dtsi#L46
--
Krystian
One dtb:
clock@1c20000 {
reg = < 0x1c20000 0x400 >;
clocks = < 0x0e 0x0f >;
clock-names = "hosc\0losc";
#clock-cells = < 0x01 >;
#reset-cells = < 0x01 >;
compatible = "allwinner,sun8i-h3-ccu";
phandle = < 0x03 >;
};
Pc2 dtb:
clock@1c20000 {
reg = < 0x1c20000 0x400 >;
clocks = < 0x0e 0x0f >;
clock-names = "hosc\0losc";
#clock-cells = < 0x01 >;
#reset-cells = < 0x01 >;
compatible = "allwinner,sun50i-h5-ccu";
phandle = < 0x03 >;
};
Stephen Graf
-----Original Message-----
From: Krystian Lewandowski <k.lewandow...@icloud.com
<mailto:k.lewandow...@icloud.com> >
Sent: February 2, 2019 10:53 AM
To: s_g...@telus.net <mailto:s_g...@telus.net>
Cc: arm@openbsd.org <mailto:arm@openbsd.org>
Subject: Re: initial cpu speed on orangepi one and orangepi pc2 - probably
other H5 and H3 boards
Wiadomość napisana przez s_g...@telus.net <mailto:s_g...@telus.net> w dniu
02.02.2019, o godz. 18:26:
I just realized that the cpu speed on these boards defaults on start-up, the
pc2 to 816Mhz and the one to 1008 Mhz. Both of these machines should be able
to run at 1300Mhz.
The pc2 speed can be changed with hw.setperf, but not the one.
Can the sxiccmu module be changed to read a value from the dtb to use as the
initial cpu speed?
Does the DT for OrangePi One have the "operating-points-v2" property?
It seems H3 is already supported by OpenBSD:
https://github.com/openbsd/src/blob/master/sys/dev/fdt/sxiccmu.c#L110
--
Krystian
