Post #1614635

While motorola-vicky is hard-bricked (waiting for UFS controller and tools to remove uMCP from the board to arrive from China), I wanted to start upstreaming patches for xiaomi-pyxis. However, I’m still not sure how to handle the touchscreen problem. I’m confident that this patch would break SHIFT6mq (shift-axolotl) which is using the same Focaltech FT5452 touchscreen, but with firmware configured for 5-point touch. Any owners of SHIFT6mq running #postmarketos that want to (potentially, temporairly) break their touchscreens by testing a patch for me? If this breaks, I will simply split FT5452 into 5 and 10-point compatible, but I’m frankly baffled this is necessary at all. Might be a hot take, but downstream does it better by specifying it in the devicetree. drivers/input/touchscreen/edt-ft5x06.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/input/touchscreen/edt-ft5x06.c b/drivers/input/touchscreen/edt-ft5x06.c index bf498bd4dea9..5cb2f7aafbb1 100644 --- a/drivers/input/touchscreen/edt-ft5x06.c +++ b/drivers/input/touchscreen/edt-ft5x06.c @@ -1476,7 +1476,7 @@ static const struct edt_i2c_chip_data edt_ft5x06_data = { }; static const struct edt_i2c_chip_data edt_ft5452_data = { - .max_support_points = 5, + .max_support_points = 10, }; static const struct edt_i2c_chip_data edt_ft5506_data = { Thanks! :neocat_heart: