09:49 <rajkosto> whats the default cpu frequency and voltage if the kernel doesnt have cpufreq for sunxi ? tho its a bit weird considering its 5.10.87

09:50 <rajkosto> on allwinner H5

11:33 <apritzel> rajkosto: that would be set in U-Boot, to 816 MHz: https://github.com/u-boot/u-boot/blob/master/arch/arm/mach-sunxi/Kconfig#L589-L598

11:34 <rajkosto> because you need to change the voltage regulator via i2c for more ?

11:36 <rajkosto> im running openwrt on the thing and i want to use the highest frequency, but it shows no cpufreq stuff in /sys/devices even though the kernel is 5.10.87, CPU_FREQ in kernel config is enabled, and so is the sy i2c, and ive replaced the dtb with the armbian one (because openwrt dtb is missing the operating points, i2c enablement, and thermal zones)

11:36 <apritzel> that's a safe value we know works without extra cooling or DVFS

11:37 <rajkosto> armbian comes with a bunch of dtb overlays regarding cpufreq though, what are they for since all the frequencies are already enabled in the base dtb ?

11:40 <rajkosto> all the cpufreq stuff should be mainline by 5.10 right

11:50 <apritzel> rajkosto: I don't think there is much actual kernel support needed for the H5, it's mostly data for the clock and regulator in the DT

11:50 <rajkosto> and im using armbian's DT now (no overlays tho)

11:51 <rajkosto> but cpufreq /sys entries are not showing up

11:54 <rajkosto> and overlays arent enabled by default, right ?

12:25 <apritzel> rajkosto: I don't know these details about Armbian, you have to ask them

12:25 <rajkosto> they are disabled, and dvfs works fine in armbian

12:26 <apritzel> you need some kernel config options enabled for DVFS to work, though

12:26 <rajkosto> pretty sure they are

12:26 <rajkosto> CPUFREQ_DT and all the governors are =y

12:33 <apritzel> and you have CONFIG_REGULATOR_SY8106A as well?

12:33 <apritzel> any hints in dmesg?

12:33 <rajkosto> yeah sy8106a is =y too

12:34 <rajkosto> nothing in dmesg

12:34 <rajkosto> cpufreq folder in sys is empty, cpu0 etc have no cpufreq folder

12:34 <rajkosto> i know im using the armbian dtb because it doesnt use correct LED names for openwrt to turn them on

12:35 <apritzel> you can double check for the nodes in /sys/firmware/devicetree/base/...

12:40 <gamiee> Hi, when you're talking about regulators, I have Banana Pi M2+, which have this switchable regulator on the board.

12:40 <gamiee> The configuration is in device-tree, so I expect that the dynamic frequency regulation works with this, although,

12:40 <gamiee> the SoC even with passive heatsink gets too hot (might be also some heat from WiFi & BT chip and RAMs). My question is,

12:40 <gamiee> is there any other way, that I can make the SoC make less heat? Or only fan?

12:40 <gamiee> (The SoC is H3)*

12:58 <rajkosto> the opp table is there that wasnt there with the openwrt dtb so yes

12:59 <rajkosto> i added "cpuidle" pm support to the kernel and that folder is showing but nothing in cpufreq

13:24 <rajkosto> cpufreq should work, as the dt contains the required fields on each cpu

13:38 <rajkosto> mv64xxx_i2c 1f02400.i2c: deferred probe timeout, ignoring dependency

13:38 <rajkosto> 1f02400 is the voltage controller i2c

22:19 <rajkosto> does "mv64xxx_i2c 1f02400.i2c: deferred probe timeout, ignoring dependency" mean pinctrl did not set up i2c properly ?

22:40 <apritzel> rajkosto: yeah, those message are often misleading

22:40 <rajkosto> i get no i2c devices so i think thats why dvfs isnt working, just no i2c buses working

22:40 <apritzel> do you see the regulator /sys/kernel/debug/regulator/regulator_summary

22:41 <rajkosto> nope

22:41 <rajkosto> only regulator-dummy and 3v3s

22:44 <apritzel> do you see both pin controllers in /sys/kernel/debug/pinctrl/pinctrl-devices

22:45 <rajkosto> name [pinmux] [pinconf]

22:45 <rajkosto> 1c20800.pinctrl yes yes

22:47 <apritzel> so nothing at 0x1f02c00?

22:48 <rajkosto> the one that works is compatible = "allwinner,sun50i-h5-pinctrl";, the one that doesnt is sun8i-h3-r-pinctrl

22:48 <rajkosto> maybe just needs a driver enabled

22:48 <apritzel> do you have CONFIG_SUN8I_R_CCU enabled?

22:49 <rajkosto> yes

22:50 <apritzel> what does /sys/kernel/debug/devices_deferred say?

22:50 <rajkosto> https://pastebin.com/D09cdnXn

22:51 <rajkosto> one that works is in pinctrl-sun50i-h5.c the one that doesnt is in pinctrl-sun8i-h3-r.c

22:52 <apritzel> I know, but we need to find out why ;-)

22:53 <apritzel> do you have CONFIG_RTC_DRV_SUN6I?

22:54 <rajkosto> PINCTRL_SUN8I_A83T_R [=y]

22:55 <rajkosto> CONFIG_RTC_DRV_SUN6I = n

22:55 <rajkosto> will try with = y

22:55 <apritzel> you need CONFIG_PINCTRL_SUN8I_H3_R also

22:56 <rajkosto> thats =y

22:56 <apritzel> it's a bit counter-intuitive, but the internal oscillator is routed through the RTC (because it can be gated there)

22:56 <rajkosto> theres no way to just jump to a search result entry in kernel menuconfig is there

22:57 <apritzel> there is

22:57 <apritzel> there is a number in parentheses on the left

22:58 <apritzel> second line from the bottom in this case, if there is only one hit then it's just (1)

22:58 <rajkosto> there sure was

22:58 <rajkosto> it goes to the parent menu first that i had to enable then jump again to the allwinner one

22:59 <apritzel> yeah, this direct jump goes wrong if a prerequisite is disabled

22:59 <apritzel> since in this case the menu entry is hidden, so the search can't take you there

23:14 <rajkosto> well that didnt help

23:16 <apritzel> any change in debugfs? does the pinctrl show up now? less output in devices_deferred?

23:16 <rajkosto> exactly the same

23:19 <rajkosto> probably because of this https://pastebin.com/K53VPxDR

23:22 <apritzel> what is your kernel, exactly?

23:23 <rajkosto> openwrt is mainline Linux OpenWrt 5.10.87 #0 SMP

23:23 <apritzel> and the DT is one from a newer kernel, I guess, post 5.13?

23:23 <rajkosto> nope, armbian is also 5.10

23:24 <rajkosto> different minor ver

23:30 <apritzel> what does "hexdump /sys/firmware/devicetree/base/soc/interrupt-controller@1f00c00/\#interrupt-cells" give you?

23:30 <rajkosto> 0000 0200

23:31 <apritzel> ok, that should work

23:32 <apritzel> (there was an incompatible DT change in 5.13, which changed this number to 3, which older kernels don't understand)

23:33 <rajkosto> im only trying this because the armbian stable and openwrt kernel trunk are same minor ver

23:34 <apritzel> yeah, but I think Armbian backports stuff from time to time, or they carry extra patches

23:35 <apritzel> the WARN message you posted points to some interrupt number misread, which could be due to a wrong #interrupt-cells number

23:40 <rajkosto> https://images.sshnuke.net/2021-12-19_00-40-32_ZU4UqHkGw.png should work tho

23:46 <apritzel> yes, the DVFS itself is not the real problem, but you are apparently missing one of its prerequisites

23:47 <apritzel> I guess the OpenWRT .config is a custom (minimal) one made by them?