Maximilian Luz

Apart from rebasing patches, commit a12d2ed4c6422c8ddb1313ceef8267291fd84fed does not have any changes at all, whereas commit 86d22a4f3e431a175224b6a6702b65beb43f59f8 only adds support for the battery "not charging" state (that can be triggered when...

@gaou-piou 5.5 does not have full IPTS/touchscreen support. On 5.5 you can either enable stylus OR enable single-touch mode (they are exclusive). See @xorpix' comment and https://github.com/linux-surface/linux-surface/issues/94#issuecomment-590118336 for details. In...

AFAIK IPTS won't be back on 5.6. There have been some issues on the Surface Go that might be resolved, though.

Is it possible that the touchscreen is misbehaving and causing those interrupts? This kinda looks like a device misbehaving to me, I'm not entirely sure how to debug this.

`INT33C2` is a I2C controller that's used for multiple I2C clients. Those seem to be (according to the DSDT but you can check that in `/sys/bus/i2c/devices/...` as well): - `MSHW0028`...

Interesting, most config options should be the same as on Fedora. Can you try unbinding the drivers for the devices I mentioned above (specifically HID ones since you mentioned that...

Interesting, IIRC `INT33C2` is an i2c controller. So this means that one controller constantly sends interrupts whereas the others work fine. It might be possible that a device connected to...

> (both disappeared after it was unbound) Yeah, that's the expected behavior. The client devices are essentially the children of the controller. So if that goes, the clients go as...

Maybe, that thing looks like a full-blown regulator, i.e. for controlling voltages, whereas (I think) the ones used on the Surface devices are for measuring only.

We've discussed the Laptop 3 on IRC. I think the Pro 7 should be fairly similar (meaning that we would need to write some sort of stub-driver which provides a...