00:30 <bryanodonoghue> vknecht[m] checked for you - I believe there's a 1:1 version match on 8916/8936/8939

00:30 <bryanodonoghue> you should focus on clocks and dtsi

04:38 <vknecht[m]> bryanodonoghue: thanks ! wrt. 1:1 version match, still possible there's an additional csid and ispf line in 8939, or is that downstream fake ?

08:25 <bryanodonoghue> downstream is true

13:14 <z3ntu> krzk: do you plan to pick up patches for dt bindings for v6.7? I see you picked up quite a few in the past but most were your own where I think you sent the PR yourself?

13:14 <z3ntu> Or in other words, should I ask Linus Walleij to pick up https://lore.kernel.org/linux-arm-msm/20230919-fp5-initial-v2-5-14bb7cedadf5@fairphone.com/ ?

19:26 <z3ntu> lumag: so for FP5 my draft redriver/retimer kernel driver seems to be operational, but getting `[ 85.622668] [drm:dp_panel_read_dpcd] *ERROR* dpcd read failed, rlen=-110` when plugging in display. Any clue what this might be? I'm not 100% confident my new driver is doing the correct things so it's possible I have messed up something there also but not sure if that error would be a symptom or something else

20:13 <konradybcio> Luca Weiss: you should probably provide lumag with a tree (unless you did so already) to look at

20:14 <konradybcio> 110 is -ETIMEDOUT, sounds almost like you can't communicate with the other thing./

22:04 <lumag> z3ntu, check that the SBU orientation is properly propagates to FSA

22:04 <lumag> because DPCD is read using AUX if I'm not mistaken

22:21 <atipls> hello, are there any guides or starting points if enabling a clock (GCC_MDSS_AXI_CLK) makes the entire system reset (msm8909)