10:05 <flowriser> I got like halfway through the ACPI dump last night so here are my questions: I see that both on the Lenovo Flex 5g and on my acer spin there are allot of i2c devices that are not in the dtb at all, so should all the i2c devices present in the dump be present in the dtb as well?

15:36 <flowriser> It appears Nvidia won't be taking over ARM

17:28 <maz> the real question is: who will?

17:32 <bamse> flowriser: some of the i2c devices have STA() methods which means that they will only be conditionally activated

17:34 <bamse> flowriser: e.g. the c630 you could get with one of two possible touchpads, both mentioned in the dsdt and the right one (indirectly) selected based on some gpio (iirc)

18:06 <steev> jebus, the next 5.16 is 1039 patches

22:46 <flowriser> bamse, huh interesting ... my device also has 3 keyboards (they show up in the device manager of Windows) :D

22:52 <robclark> just a guess, but different language keyboards are different sometimes (in # of keys, etc)

23:05 <flowriser> robclark, that might explain some weirdness I found last night when I enabled another i2c/hid device in the dtb and the keyboard started "working": no backspace and some characters not registering

23:07 <flowriser> Also I have no USB when using the dtb, but one problem at a time

23:09 <flowriser> Found a whole sleuth of chips in the ACPI that I have no idea what they do; some AI chips, jpeg encoders and some other stuff. The wacom pen is also there, some proximity sensors, etc

23:46 <bamse> flowriser: i believe that's in addition to the hardware-variations that are expressed in the dsdt

23:49 <robclark> ai, jpeg encoder, etc would be different ip blocks (not separate chips).. no idea to what extent windows makes use of 'em

23:50 <HdkR> Oh no way, jpeg encoder? mjpeg for conference applications or something?

23:51 <robclark> maybe more likely a jpeg decoder?

23:51 <bamse> if you run the qualcomm camera stack i bet they encode the jpegs using the jpeg block

23:51 <bamse> robclark: i think it can decode, but in particular it encodes

23:51 <robclark> hmm, ok, that's possible too

23:52 <robclark> I'll remember that next time I take my camera-laptop with me :-P

23:52 <bamse> flowriser: and you missed the "FD" block, which is short for "face detector"

23:52 <bamse> robclark: should be able to expose that as some sort of m2m v4l2 device...but i don't know if anything in userspace would use it

23:53 <bamse> the jpeg thing i mean

23:53 <robclark> does windows do face-unlock?

23:53 <bamse> robclark: yeah...since i got windows 11 on the prox it keeps telling me that i should enable that, pretty much every time i unlock it

23:53 <robclark> IIRC on CrOS they do use hw jpg decode on some devices

23:53 <bamse> robclark: interesting

23:54 <robclark> the instagram accelerator, I guess?

23:54 <bamse> hehe

23:55 <bamse> but the face-detect will detect faces, not your face

23:55 <bamse> not your specific face

23:55 <bamse> that would likely be something they run on the cdsp