14:50 <warpme> guys: I just upgraded rock4b (rk3399) from well working 6.1 to 6.2 and....nothing on hdmi. dmesg: https://termbin.com/uxsrz Pls look i.e around: 2.028098 Is this known issue of 6.2? For me it looks like regression?

15:18 <robmur01> warpme: I see no sign of the HDMI driver loading - maybe check your config/modules?

15:21 <robmur01> in fact you've got a whole load of stuff failing to probe properly and deferring

15:26 <robmur01> yeah, that error from the PMIC driver may well be why

15:26 <warpme> oh well - the same 6.2 kernel config (and os binary image) works well on 3328/3566/3568. only started to 3399 fail. Only change is: kernel 6.1->6.2. Looking on working 6.1 vs non working 6.2 dmesg: in 6.2 i stared to have errors like "rockchip-pinctrl pinctrl: could not request pin 53 (gpio1-21) from group pmic-int-l on device rockchip-pinctrl". I looked on DT changes and nothing there....

15:30 <warpme> pin53 is https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi?h=v6.2#n579

15:31 <warpme> in dmesg is see: "pinctrl: pin gpio1-21 already requested by 0-001b; cannot claim for rk808-regulator.1.auto"

15:32 <robmur01> there has been some refactoring in the GPIO/pinctrl drivers fairly recently - I'd guess it's something to do with the interrupt trying to claim the pin and colliding with the explicit pinctrl claim

15:33 <robmur01> quite possibly because it's the MFD driver that owns the pinctrl, but the regulator driver trying to claim the interrupt

15:36 <robmur01> if you have time, bisecting between 6.1 and 6.2 should help narrow down which subsystem's behaviour changed, then it should be clearer which driver(s) to dig into

15:49 <warpme> argh - i was hoping to find most probable regressing commit by scanning commits log. nothing comes to me....

19:34 <warpme> : robmur01: fyi: i found root cause: it is hunk in h616 patch which was needed for 6.1 -but not needed anymore for 6.2. Now all works ok. many thanx for help!