03:43 <JensGlathe[m]> konradybcio: Yes, unfortnately. `qcom-rpmhpd 18200000.rsc:power-controller: sync_state() pending due to ad00000.clock-controller` Only on Volterra where I have this modle blacklisted, though

03:44 <JensGlathe[m]> If i disable this clock controller in the sc8280xp.dtsi, things don't get better, so it is required for something

08:10 <\[m]> how does one have a dev kit yet??

08:23 <JensGlathe[m]> waiting for mine

08:41 <maz> supposed to be shipping today. somehow, I don't believe it.

09:15 <JensGlathe[m]> says the same on my order, but looks further processed than last time

09:17 <maz> still in the "submitted" state for me, just like it has been for over two months.

09:22 <JensGlathe[m]> Guess why I have an x1e laptop now - that was my excuse

09:24 <JensGlathe[m]> its on ["black week" or something](https://www.hp.com/de-de/shop/product.aspx?id=a3ny2ea&opt=abd&sel=ntb) btw

09:28 <JensGlathe[m]> How can I scan where i2c devices are... I activated all i2c buses that are listed as active on Windows (according to HWInfo ARM64), matched by address. I could take the keyboard definition and try them through, bu maybe there is a tool to get info what's on these buses?

09:33 <JensGlathe[m]> There are also 3 buses not yet declared in x1e80100.dtsi

09:33 <JensGlathe[m]> `@a04000` with interrupts 776 and 777

09:33 <JensGlathe[m]> `@b04000` with interrupts 588 and 589

09:34 <JensGlathe[m]> * There are also 3 buses not yet declared in x1e80100.dtsi... (full message at <https://matrix.org/oftc/media/v1/media/download/AaKIfusk6gnt7RJ-ZG28nXcJ7vk5tNdamQCT07PBOSJebB-Xs-2qrpWHQsyVrcQx577-lDzopPo4AeOsb0lktqJCeSBjMNUwAG1hdHJpeC5vcmcvU3hVUUVMeEx6TlFwZHdKTVpCV2hCTVla>)

09:36 <JensGlathe[m]> maybe USB related (also three xhci controllers)?

10:49 <konradybcio> Jens Glathe: no sync state means all interconnect paths are running at max speeds

10:49 <konradybcio> (bad)

12:35 <JensGlathe[m]> yeah. Getting that bSOD is even worse

12:35 <JensGlathe[m]> I would like to avoid it, sure

13:52 <JensGlathe[m]> hmm internal kb on HP X14 is working now, its i2c0 (like the touchpad)

14:11 <JensGlathe[m]> and both work

15:23 <spawacz> steev: https://0x0.st/s/-Yag5h7Sg2csw4yNeLoVpA/X3Ll.txt

18:12 <MrCatfood[m]> anyone has a bootable image for the vivo book?

18:14 <JensGlathe[m]> Ubuntu desktop preinstalled, yes

18:15 <JensGlathe[m]> Anybody got a touchscreen running on x1e Notebooks?

18:56 <kuruczgy[m]> Jens Glathe: on the yoga it has been working flawlessly for me since the beginning, it's just an hid over i2c device AFAIK

18:57 <JensGlathe[m]> hmm mine is VEN_ELAN&DEV_2513&SUBSYS_CRD08380

18:57 <JensGlathe[m]> somebody got some humour

18:57 <JensGlathe[m]> touchscreen?

19:00 <kuruczgy[m]> Yeah, as I said on the yoga all three input devices (touchscreen, touchpad, keyboard) are hid-over-i2c, and all have been working flawlessly for me

19:01 <kuruczgy[m]> > VEN_ELAN&DEV_2513&SUBSYS_CRD08380

19:01 <kuruczgy[m]> Not sure what this device path is, looks kinda cursed...

19:03 <JensGlathe[m]> oh I've seen something, thanks

19:19 <JensGlathe[m]> Touchscreen works now. It's the complete touchscreen definition from the CRD (as the subsystem ID suggests). I copied the definition from the yoga 7, and they are almost identical. CRD uses address 0x10, yoga 0x14.

19:26 <steev> spawacz: can i see your dmesg output as well?

19:26 <spawacz> steev: give me a minute

19:26 <steev> no rush :)

19:29 <spawacz> Sent you a private message with the link

19:34 <konradybcio> Jens Glathe: there's no point in guessing, hid-over-i2c is described in acpi

19:35 <JensGlathe[m]> HP X14 seems to be very close to CRD ACPI and hw wise

21:39 <steev> https://patchwork.kernel.org/project/linux-arm-msm/patch/20240918-x1e-fix-pdm-pdr-v1-1-cefc79bb33d1@linaro.org/ for you x1e's

21:54 <JosDehaes[m]> Will that unbreak the kernel pd mapper?

22:03 <steev> i do not have an x1e, so... maybe?