Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Merge tag 'input-for-v5.19-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input

Pull input fixes from Dmitry Torokhov:

- fix Goodix driver to properly behave on the Aya Neo Next

- some more sanity checks in usbtouchscreen driver

- a tweak in wm97xx driver in preparation for remove() to return void

- a clarification in input core regarding units of measurement for
resolution on touch events.

* tag 'input-for-v5.19-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
Input: document the units for resolution of size axes
Input: goodix - call acpi_device_fix_up_power() in some cases
Input: wm97xx - make .remove() obviously always return 0
Input: usbtouchscreen - add driver_info sanity check

+18 -5
+5
drivers/input/touchscreen/goodix.c
··· 900 900 } else { 901 901 dev_warn(dev, "Unexpected ACPI resources: gpio_count %d, gpio_int_idx %d\n", 902 902 ts->gpio_count, ts->gpio_int_idx); 903 + /* 904 + * On some devices _PS0 does a reset for us and 905 + * sometimes this is necessary for things to work. 906 + */ 907 + acpi_device_fix_up_power(ACPI_COMPANION(dev)); 903 908 return -EINVAL; 904 909 } 905 910
+3
drivers/input/touchscreen/usbtouchscreen.c
··· 1654 1654 if (id->driver_info == DEVTYPE_IGNORE) 1655 1655 return -ENODEV; 1656 1656 1657 + if (id->driver_info >= ARRAY_SIZE(usbtouch_dev_info)) 1658 + return -ENODEV; 1659 + 1657 1660 endpoint = usbtouch_get_input_endpoint(intf->cur_altsetting); 1658 1661 if (!endpoint) 1659 1662 return -ENXIO;
+3 -1
drivers/input/touchscreen/wm97xx-core.c
··· 758 758 759 759 static int wm97xx_mfd_remove(struct platform_device *pdev) 760 760 { 761 - return wm97xx_remove(&pdev->dev); 761 + wm97xx_remove(&pdev->dev); 762 + 763 + return 0; 762 764 } 763 765 764 766 static int __maybe_unused wm97xx_suspend(struct device *dev)
+7 -4
include/uapi/linux/input.h
··· 78 78 * Note that input core does not clamp reported values to the 79 79 * [minimum, maximum] limits, such task is left to userspace. 80 80 * 81 - * The default resolution for main axes (ABS_X, ABS_Y, ABS_Z) 82 - * is reported in units per millimeter (units/mm), resolution 83 - * for rotational axes (ABS_RX, ABS_RY, ABS_RZ) is reported 84 - * in units per radian. 81 + * The default resolution for main axes (ABS_X, ABS_Y, ABS_Z, 82 + * ABS_MT_POSITION_X, ABS_MT_POSITION_Y) is reported in units 83 + * per millimeter (units/mm), resolution for rotational axes 84 + * (ABS_RX, ABS_RY, ABS_RZ) is reported in units per radian. 85 + * The resolution for the size axes (ABS_MT_TOUCH_MAJOR, 86 + * ABS_MT_TOUCH_MINOR, ABS_MT_WIDTH_MAJOR, ABS_MT_WIDTH_MINOR) 87 + * is reported in units per millimeter (units/mm). 85 88 * When INPUT_PROP_ACCELEROMETER is set the resolution changes. 86 89 * The main axes (ABS_X, ABS_Y, ABS_Z) are then reported in 87 90 * units per g (units/g) and in units per degree per second