14:56 <hexdump0815> xdarklight: upgraded my mxq to 5.1.5 and used your latest mxq dtb - it runs fine, but i noticed two things: the temperature sensor is not working (no hwmon or thermal) and there are quite a few pwm regulator warnings plus some from dwc2

14:56 <hexdump0815> here is the bootlog: https://pastebin.com/raw/CWBCuWnF

14:58 <hexdump0815> any idea what might be wrong or missing for the thermal sensor? are the pwm and dwc warnings a problem? the system runs very stable already since v5.0 even under heavy load

15:44 <xdarklight> hexdump0815: can you please show me your .config as well?

15:45 <xdarklight> the dwc2 warnings are "normal", you can ignore them (I believe a patch which fixes them is queued for v5.2 or v5.3 because it affects more than just the Amlogic SoCs)

15:47 <xdarklight> then these "pwm-regulator regulator-vcck: Failed to get PWM" warnings are fine as well *if* the pwm-meson driver is built as module (and thus loaded "later" in the boot process). check the output of "cat /sys/kernel/debug/pwm" to verify that it was loaded correctly later on

15:49 <xdarklight> that leaves us with the temperature sensor issue, you simply might be missing two kernel .config options here as these are only queued for multi_v7_defconfig for v5.2 (but will still work with 5.1): https://patchwork.kernel.org/patch/10875957/

16:38 <hexdump0815> xdarklight: this is the kernel config used - https://pastebin.com/raw/7btntFFV - i'll check and rebuild with the options as you recommended - thanks for the quick response

16:46 <hexdump0815> meson-pwm was built as a module as you suspected, CONFIG_MESON_SARADC was in but not as a module and CONFIG_MESON_MX_EFUSE was not in ... kernel rebuild is running

16:48 <xdarklight> fingers crossed!

16:56 <hexdump0815> xdarklight: it helped - temperature is there now and now more pwm warnings \o/ :)

16:56 <hexdump0815> no more warnings i ment ...

16:59 <hexdump0815> btw. i have an m8s meson8m2 here now too to help testing for this one a bit as well - still have to solder the serial console to it ... do you know if it should work with the supplied dtbs?

17:06 <xdarklight> nice :)

17:08 <xdarklight> regarding your M8S: I also have that, but I'm not sure if there are multiple variants out there

17:08 <xdarklight> mine has fixed VCCK and VDDEE voltage regulators

17:08 <xdarklight> the vendor Android constantly limits it to 1.2GHz, no CPU frequency scaling

17:09 <xdarklight> if yours is similar then the .dts from my tree might work

17:37 <hexdump0815> xdarklight: just had a look at the meson8 opp-table, so the m8s will then be limited to 1.2 ghz in mainline too - right? i.e. maybe even slower than the mxq :)

17:38 <xdarklight> yep

17:39 <xdarklight> I haven't measured if it's actually slower (Cortex-A5 cores in the MXQ vs Cortex-A9 cores in the M8S), I never measured the difference

20:22 <xdarklight> ukleinek: thank you for taking the time to go through the patch I came up with and the detailed explanation/reply!