On 8/18/25 7:28 AM, Jonathan Denose wrote:
> From: Angela Czubak <aczubak@xxxxxxxxxx>
>
> INPUT_PROP_HAPTIC_TOUCHPAD property is to be set for a device with simple
> haptic capabilities.
>
> Signed-off-by: Angela Czubak <aczubak@xxxxxxxxxx>
> Co-developed-by: Jonathan Denose <jdenose@xxxxxxxxxx>
> Signed-off-by: Jonathan Denose <jdenose@xxxxxxxxxx>
> ---
> Documentation/input/event-codes.rst | 14 ++++++++++++++
> include/uapi/linux/input-event-codes.h | 1 +
> 2 files changed, 15 insertions(+)
>
> diff --git a/Documentation/input/event-codes.rst b/Documentation/input/event-codes.rst
> index b4557462edd7b3fef9e9cd6c2c3cb2d05bb531ab..6f7aa9e8207c4aa825d9694ad891f4d105fe8196 100644
> --- a/Documentation/input/event-codes.rst
> +++ b/Documentation/input/event-codes.rst
> @@ -400,6 +400,20 @@ can report through the rotational axes (absolute and/or relative rx, ry, rz).
> All other axes retain their meaning. A device must not mix
> regular directional axes and accelerometer axes on the same event node.
>
> +INPUT_PROP_HAPTIC_TOUCHPAD
> +--------------------------
> +
> +The INPUT_PROP_HAPTIC_TOUCHPAD property indicates that device:
> +- supports simple haptic auto and manual triggering
> +- can differentiate between at least 5 fingers
> +- uses correct resolution for the X/Y (units and value)
> +- report correct force per touch, and correct units for them (newtons or grams)
reports
> +- follows the MT protocol type B
> +
> +Summing up, such devices follow the MS spec for input devices in
--
~Randy
