narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
Darkmatter66 has quit [Ping timeout: 272 seconds]
Darkmatter66 has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
vagrantc has quit [Quit: leaving]
sputnik_ has joined #linux-amlogic
chewitt has joined #linux-amlogic
chewitt has quit [Quit: Adios!]
Darkmatter66 has quit [Ping timeout: 246 seconds]
chewitt has joined #linux-amlogic
The_Coolest has joined #linux-amlogic
Darkmatter66 has joined #linux-amlogic
warpme_ has joined #linux-amlogic
warpme_ has quit [Quit: warpme_]
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #linux-amlogic
warpme_ has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 248 seconds]
Darkmatter66 has joined #linux-amlogic
warpme_ has quit [Quit: warpme_]
_whitelogger has joined #linux-amlogic
chewitt has quit [Ping timeout: 272 seconds]
Darkmatter66 has quit [Ping timeout: 252 seconds]
warpme_ has quit [Quit: warpme_]
_whitelogger has joined #linux-amlogic
hexdump0815 has joined #linux-amlogic
<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
<hexdump0815> here is the bootlog: https://pastebin.com/raw/CWBCuWnF
<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
<xdarklight> hexdump0815: can you please show me your .config as well?
<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)
<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
<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/