15:32 <aka_[m]> Which way of handling i2c device init is better?

15:32 <aka_[m]> Keep adding compatibles for each device or use fwloader to load .bin file and reading u8 of it parsing pair of reg,value or adding init-seqs under dts in pairs?

15:32 <aka_[m]> i feel like DT is best for it but not sure

15:47 <flamingradian[m]> is it too big for the driver?

15:56 <Pan[m]> <Pan[m]> "Okay, aparently on elish only..." <- slpi fails to load on sm8150 (nabu, vayu) and sm8250 devices (xiaomi-lmi), did you had to do anything related to it to get it working?, or is it something about xiaomi messing with the firmware in a way manline can't load it

16:01 <flamingradian[m]> Pan: oh, uh there was a missing sleepstate node in smp2p that caused crashes every 10 sec

16:04 <Pan[m]> flamingradian[m]: oh, could you point me into that?

16:14 <flamingradian[m]> probably isn't an applicable fix if the crashing happens while connecting, but an example is here: https://gitlab.com/sdm670-mainline/linux/-/blob/sdm670-v6.11.3/arch/arm64/boot/dts/qcom/sdm670.dtsi#L549

16:15 <flamingradian[m]> looking at your dmesg again, it could have something to do with `qmi_decode_string_elem: String len 128 >= Max Len 65`

19:35 <Pan[m]> <flamingradian[m]> "looking at your dmesg again..." <- yeah, every of the devices i saw have the same error but with different values