Linux Kernel 4.18.8

[dukla2000]

Saw this on your forums - many thanks to av (or whoever has done the cooking)!

Seems like a couple of things are improved since rc8 (e.g. DRM-ROCKCHIP doesn't cause major delays/timeouts) - I hope you are OK if I use this thread to list problems I have with 4.18 (in fact 4.18.8 now)?

1) The video/armsoc/DRM/midgard is not quite right. Sorry my knowledge in this area is dangerous so apologies for any terminology abuses. The most obvious problem is in Xorg.log

Code:

[    36.693] (II) ARMSOC: Driver for ARM Mali compatible chipsets
[    36.693] (WW) Falling back to old probe method for armsoc
[    36.693] (II) No BusID or DriverName specified - opening /dev/dri/card0
[    36.693] (EE) ERROR: Cannot set the DRM interface version.
[    36.693] (EE) ERROR: Cannot open a connection with the DRM - Permission denied

Not sure if the early failure to bind to HDMI is significant?

Code:

$ dmesg | grep drm
[    1.419355] rockchip-drm display-subsystem: Linked as a consumer to ff8f0000.vop
[    1.420145] rockchip-drm display-subsystem: Linked as a consumer to ff900000.vop
[    1.421531] rockchip-drm display-subsystem: Linked as a consumer to ff940000.hdmi
[    1.426903] rockchip-drm display-subsystem: bound ff8f0000.vop (ops vop_component_ops)
[    1.429626] rockchip-drm display-subsystem: bound ff900000.vop (ops vop_component_ops)
[    1.430571] rockchip-drm display-subsystem: failed to bind ff940000.hdmi (ops dw_hdmi_rockchip_ops): -517
[    1.431852] rockchip-drm display-subsystem: master bind failed: -517
[    2.255270] rockchip-drm display-subsystem: bound ff8f0000.vop (ops vop_component_ops)
[    2.257496] rockchip-drm display-subsystem: bound ff900000.vop (ops vop_component_ops)
[    2.259748] rockchip-drm display-subsystem: bound ff940000.hdmi (ops dw_hdmi_rockchip_ops)
[    2.260483] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.261066] [drm] No driver support for vblank timestamp query.
[    2.478338] rockchip-drm display-subsystem: fb0:  frame buffer device
[    2.480186] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0

2) Sound - no chance on HDMI but seems almost there on ES8316 but not quite again. And again my skills around sound are pathetic. The first time I try to play something with mpv the screen looks like it is playing, but nothing comes through the speakers, and dmesg has

PHP Code:

[ 1002.035173] es8316 1-0010: No sysclk provided
[ 1002.035579] es8316 1-0010: ASoC: can't open codec ES8316 HiFi: -22
[ 1002.040228] es8316 1-0010: No sysclk provided
[ 1002.040628] es8316 1-0010: ASoC: can't open codec ES8316 HiFi: -22
[ 1002.043697] es8316 1-0010: No sysclk provided
[ 1002.044221] es8316 1-0010: ASoC: can't open codec ES8316 HiFi: -22
[ 1002.045391] es8316 1-0010: No sysclk provided
[ 1002.045787] es8316 1-0010: ASoC: can't open codec ES8316 HiFi: -22
[ 1002.047267] es8316 1-0010: No sysclk provided
[ 1002.047669] es8316 1-0010: ASoC: can't open codec ES8316 HiFi: -22
[ 1002.048943] es8316 1-0010: No sysclk provided
[ 1002.049340] es8316 1-0010: ASoC: can't open codec ES8316 HiFi: -22 


3) The schedulling is not right: with either ondemand or performance high CPU jobs land on the little cores. I guess CONFIG_ARM_ROCKCHIP_CPUFREQ needs to be ported from 4.4?

4) Still get an infinite loop at boot "running CQE recovery" if eMMC is plugged in

5) This seems to be a defect in the DT but I cannot find it:

Code:

$ dmesg | grep vcc_sdio
[    2.092922] vcc_sdio: Bringing 3300000uV into 3000000-3000000uV
[    2.148951] vcc_sdio: unsupportable voltage range: 3300000-3000000uV

6) Similarly think this is an attempt to define OTG on USB2 whereas it should be the USB3 ports

Code:

$ dmesg | grep otg
[    1.818420] OF: graph: no port node found in /syscon@ff770000/usb2-phy@e450/otg-port